Skip to content

Commit eb8f936

Browse files
authored
Update concept.md
1 parent 14f20b6 commit eb8f936

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

docs/advanced/technical/concept.md

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -133,37 +133,44 @@ PICPICPICPIC
133133
A central feature of HTML Over the Wire is that only the affected parts of the page are updated, rather than the entire document. Can this be achieved in UI5? While altering the XML view would typically trigger a full re-render, updating only the view model and binding attributes accordingly allows UI5 to update just the relevant UI elements. Consider this example:
134134

135135
```abap
136-
CLASS z2ui5_cl_app_partly_rerender DEFINITION PUBLIC CREATE PUBLIC.
136+
CLASS z2ui5_cl_demo_app_025 DEFINITION PUBLIC CREATE PUBLIC.
137137
138138
PUBLIC SECTION.
139139
INTERFACES z2ui5_if_app.
140140
DATA text TYPE string.
141+
DATA partly TYPE abap_bool.
141142
142143
ENDCLASS.
143144
144-
CLASS z2ui5_cl_app_partly_rerender IMPLEMENTATION.
145+
CLASS z2ui5_cl_demo_app_025 IMPLEMENTATION.
145146
146147
METHOD z2ui5_if_app~main.
147148
148-
IF client->check_on_init( ).
149+
text = text && ` text`.
150+
151+
IF client->check_on_init( ) OR partly = abap_false.
149152
client->view_display( z2ui5_cl_xml_view=>factory(
150-
)->input( value = client->_bind( text )
151-
)->button( text = 'partly rerender html' press = client->_event( 'POST' ) ).
153+
)->input( client->_bind( text )
154+
)->input( submit = client->_event( )
155+
)->checkbox( selected = client->_bind_edit( partly ) text = `partly` ) ).
156+
152157
ELSE.
153-
text = text && ` text`.
154158
client->view_model_update( ).
155159
ENDIF.
156160
157161
ENDMETHOD.
158162
159163
ENDCLASS.
160164
```
161-
165+
you can see in comparison, partly vs not:
166+
![party](https://github.com/user-attachments/assets/79a8c531-b9a0-4bf4-bb1c-7d9019ef8707)
167+
All credits go here to the beatigul ui5 framework, it checks automatically for view model updates and only rerenderd the necessary controls. always keep in min to resend the view as selten as pssible but becaue i ttriggers w whole rerender cisotn gperfomrance and a bda ux experience. always try to only use
162168
```abap
163169
client->view_model_update( ).
164170
```
171+
you also see the that the fcus stays stable giving the user has a great expereince, and done with a couple of lines of abap. this is all wenn need to call it UI5 over-the-wire.
165172

166-
#### What about RAP?
173+
#### Isnt RAo aso also a bakcend driven and similar?
167174

168175
Although RAP [(3)](https://pages.community.sap.com/topics/abap/rap) shifts more logic and development to the backend, it cannot be considered an “over-the-wire” approach:
169176
- RAP focuses on defining data models (CDS), services, and transactional logic in ABAP, exposing them via OData endpoints consumed by the frontend

0 commit comments

Comments
 (0)