Skip to content

Commit e7bf90d

Browse files
authored
Update overview.md
1 parent f4155d3 commit e7bf90d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/advanced/technical/overview.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
# Technology Evolution: From ITS to abap2UI5
22

3-
This page explains how SAP UI technologies have evolved over the years — from classic Server-Side Rendering approaches like **ITS** and **Web Dynpro**, to client-side SPAs with **UI5 Freestyle** and **RAP**, and finally to the **Over-the-Wire** paradigm of **abap2UI5**.
3+
This page explains how web development in the SAP Environment has evolved over the years — from classic Server-Side Rendering approaches like **ITS** and **Web Dynpro**, to client-side SPAs with **UI5 Freestyle** and **RAP**, and finally to the **Over-the-Wire** paradigm of **abap2UI5**.
44

5-
### 1. ITS Mobile: Bringing SAP GUI to the Web (2000+)
5+
### 1. ITS Mobile: Bringing SAP GUI to the Web (2000+) (SAP)
66
The **Internet Transaction Server (ITS)** was SAP’s first step to bring SAP GUI screens (Dynpro) to the web. ITS Mobile converts classical Dynpro screens into basic HTML pages.
77

88
- Pure **Server-Side Rendering (SSR)**: HTML is generated on the server for every interaction.
99
- Optimized for simple mobile devices (e.g., warehouse scanners).
1010
- Focus on reusing existing Dynpro logic for web & mobile use cases.
1111
- Still used today for specific legacy scenarios.
1212

13-
### 2. Web Dynpro ABAP: Structured Web Applications (2003+)
13+
### 2. Web Dynpro ABAP: Structured Web Applications (2003+) (SAP)
1414
**Web Dynpro ABAP** introduced a component-based UI framework for web applications.
1515

1616
- UI definitions are created in ABAP (Views, Context, Controllers).
1717
- Still **Server-Side Rendering**: UI is built on the server, rendered as HTML in the browser.
1818
- Suitable for transactional business applications.
1919
- More structured and modular than ITS, but limited for modern UX expectations.
2020

21-
### 3. UI5 Freestyle: Full Client-Side SPAs (2010+)
21+
### 3. UI5 Freestyle: Full Client-Side SPAs (2010+) (SAP)
2222
With the advent of smartphones and richer web experiences, **UI5 Freestyle** was introduced.
2323

2424
- Based on **JavaScript, XML Views, and UI5 Controls**.
@@ -27,15 +27,15 @@ With the advent of smartphones and richer web experiences, **UI5 Freestyle** was
2727
- Enables highly customized, interactive applications.
2828
- Requires dedicated frontend development expertise.
2929

30-
### 4. RAP / Fiori Elements: Standardized Backend-Driven SPA (2019+)
30+
### 4. RAP / Fiori Elements: Standardized Backend-Driven SPA (2019+) (SAP)
3131
The **RESTful Application Programming Model (RAP)** and **Fiori Elements** aim to standardize application development.
3232

3333
- Developers define **CDS Annotations** in ABAP to describe UI behavior.
3434
- The UI5 Fiori Elements runtime in the browser renders the app as a **SPA**.
3535
- Simplifies UI development by using predefined floorplans and templates.
3636
- Still SPA complexity (OData Metadata handling, UI5 runtime in browser).
3737

38-
### 5. abap2UI5: Over-the-Wire for SAP (2023+)
38+
### 5. abap2UI5: Over-the-Wire for ABAP/UI5 (2023+) (Open Soure)
3939
**abap2UI5** brings the simplicity of the **Over-the-Wire** concept to SAP UI5 development.
4040

4141
- The ABAP backend defines **UI5 XML Views** and **JSON ViewModels**.

0 commit comments

Comments
 (0)