Skip to content

Commit 914ede4

Browse files
authored
Update concept.md
1 parent a17f371 commit 914ede4

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,7 +103,7 @@ 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/9aa09a7f-5931-496d-bf88-d9b34653784c" />
106+
<img width="300" 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>
@@ -127,7 +127,7 @@ If we continued relying on OData, updates would typically be routed into the ODa
127127
Let’s take a closer look at a key UI5 feature: the concept of view models. In UI5 freestyle, view models are used to bind attributes such as visible or enabled — allowing control properties in the view to be mapped precisely to model attributes:
128128

129129
<p align="center">
130-
<img width="350" alt="image" src="https://github.com/user-attachments/assets/7eaa09d3-e3f7-4ebb-997d-fc68cc68421f" />
130+
<img width="340" alt="image" src="https://github.com/user-attachments/assets/7eaa09d3-e3f7-4ebb-997d-fc68cc68421f" />
131131
<br/>
132132
<em>UI5 View Model Concept – UI control properties are bound to View Model attributes</em>
133133
</p>

0 commit comments

Comments
 (0)