Skip to content

Commit 5a5578e

Browse files
authored
Update concept.md
1 parent 0da1c78 commit 5a5578e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/technical/concept.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,15 +103,15 @@ When a user triggers an event (e.g., pressing a button), the event information i
103103
In standard UI5 freestyle applications, each app requires its own dedicated set of frontend artifacts:
104104

105105
<p align="center">
106-
<img width="350" alt="image" src="https://github.com/user-attachments/assets/abfe4163-e75d-4eab-ad4c-621f693fa6c3" />
106+
<img width="350" alt="image" src="https://github.com/user-attachments/assets/9aa09a7f-5931-496d-bf88-d9b34653784c" />
107107
<br/>
108108
<em>UI5 freestyle – Each application requires its own set of deployed UI and App artifacts</em>
109109
</p>
110110

111111
With abap2UI5, the frontend becomes a static UI5 shell shared across all applications. Views and logic are fully defined and maintained in the backend. Each application is represented by a single ABAP class that generates the view and handles events:
112112

113113
<p align="center">
114-
<img width="350" alt="image" src="https://github.com/user-attachments/assets/646c10e3-ef82-403f-8538-9efe45836ca2" />
114+
<img width="400" alt="image" src="https://github.com/user-attachments/assets/2d8b6441-84f3-464c-980f-2773d619af29" />
115115
<br/>
116116
<em>abap2UI5 – Shared shell app, each application is represented by backend ABAP classes</em>
117117
</p>

0 commit comments

Comments
 (0)