|
2 | 2 |
|
3 | 3 | The key concept of **abap2UI5** is to apply the **HTML Over-the-Wire** concept to SAP UI5 application development. |
4 | 4 |
|
5 | | -**HTML Over-the-Wire** refers to a web architecture where the server renders user interfaces and sends ready-to-use HTML fragments to the browser. This avoids complex client-side frameworks and keeps the frontend lightweight and maintainable. |
| 5 | +**HTML Over-the-Wire** refers to a web architecture where the server renders user interfaces and sends ready-to-use HTML fragments to the browser. This avoids complex client-side frameworks and keeps the frontend lightweight and maintainable. The UI and Business Logic stays on the server. |
6 | 6 |
|
7 | 7 | ```plaintext |
8 | | -+---------------------+ +------------------+ +-------------------+ |
9 | | -| Backend | | Browser | | User | |
10 | | -|---------------------| |------------------| |-------------------| |
11 | | -| HTML Definition | --> | Receives Response| --> | Interacts with UI | |
12 | | -| | | Renders UI | | (clicks, inputs) | |
13 | | -+---------------------+ +------------------+ +-------------------+ |
| 8 | ++-------------------+ +------------------+ +-------------------+ |
| 9 | +| Server | | Browser | | User | |
| 10 | +|-------------------| |------------------| |-------------------| |
| 11 | +| HTML Definition | --> | Receives Response| --> | Interacts with UI | |
| 12 | +| | | Renders UI | | (clicks, inputs) | |
| 13 | ++-------------------+ +------------------+ +-------------------+ |
14 | 14 | ``` |
15 | 15 | Flow: |
16 | | -- The backend defines HTML |
| 16 | +- The server defines HTML |
17 | 17 | - The browser inserts these Definitions |
18 | 18 | - Users interact with the UI — the backend handles logic and updates |
19 | 19 |
|
@@ -56,9 +56,9 @@ Several frameworks successfully implement the HTML over-the-wire approach: |
56 | 56 | | [Unpoly](https://unpoly.com) | Simplified partial page updates | Any web stack | |
57 | 57 |
|
58 | 58 |
|
59 | | -### From HTML to UI5 Over-the-Wire |
| 59 | +### UI5 Over-the-Wire |
60 | 60 |
|
61 | | -In this architecture, the UI is defined on the ABAP server and transmitted to the browser. The browser renders the interface using a static UI5 application — without requiring additional JavaScript logic, OData services, or frontend frameworks. |
| 61 | +So how can a UI5 over-the-wire approach look like? In this architecture, the UI is defined on the ABAP server and transmitted to the browser. The browser renders the interface using a static UI5 application — without requiring additional JavaScript logic, OData services, or frontend frameworks. |
62 | 62 |
|
63 | 63 | ```plaintext |
64 | 64 | +---------------------+ +------------------+ +-------------------+ |
|
95 | 95 | - Offline functionality or complex client-side interactions are not covered. |
96 | 96 | - Less effective if frontend and backend teams work independently. |
97 | 97 |
|
| 98 | +#### Partly updates of the HTML page |
| 99 | +One key feature is that the browser that the browser does ot rerender all the html but only specific parts. Are we ablte to adapt this with UI5. While changing the XML view would cause a complete rerender process, by foucsn on view model updates ony and binding ui attribtues to the model, the ui5 framwork automtically update only specific psrt. Try out this snippet: |
| 100 | +```abap |
| 101 | +
|
| 102 | +``` |
| 103 | +Ist that beatuiful? |
| 104 | + |
98 | 105 | ### Summary |
99 | 106 |
|
100 | 107 | The **key concept of abap2UI5** is to bring the simplicity and efficiency of the HTML Over-the-Wire pattern into the SAP ecosystem. |
|
0 commit comments