|
| 1 | +# abap2UI5 Compared to UI5, RAP & Over-the-Wire Frameworks |
| 2 | + |
| 3 | +This page compares **abap2UI5** with modern "HTML Over the Wire" frameworks like **htmx**, **Phoenix LiveView**, and **Laravel Livewire**. |
| 4 | + |
| 5 | +The goal is to show how abap2UI5 combines Over-the-Wire simplicity with SAP-specific technologies, offering a lightweight alternative for UI5 development. |
| 6 | + |
| 7 | +## Comparison: abap2UI5 vs htmx / LiveView / Livewire |
| 8 | + |
| 9 | +| Concept | abap2UI5 | htmx / LiveView / Livewire | |
| 10 | +|---------------------------|--------------------------------------------------------|-------------------------------------------------------------| |
| 11 | +| **UI Rendering** | ABAP generates UI5 XML Views, rendered in browser | Server renders HTML, sends fragments to browser | |
| 12 | +| **Frontend knowledge** | Frontend app only renders Views & Data, no app logic | Browser is "dumb", no application state or logic | |
| 13 | +| **Interactivity** | UI events trigger AJAX calls to ABAP backend | Events trigger AJAX/WebSocket calls to backend | |
| 14 | +| **State Management** | Backend holds full application state, Drafts simulate session | Backend maintains state (LiveView: WebSockets, Livewire: stateless diffs) | |
| 15 | +| **Delta Rendering** | View & Data sent as JSON diff, only updated controls re-rendered | HTML diffs / fragments sent, partial DOM updates | |
| 16 | +| **APIs required?** | Simple HTTP handler, no OData/CDS | No explicit API, server returns ready-to-render UI | |
| 17 | +| **Frontend development effort** | No custom JS needed, pure ABAP | Minimal JS, declarative HTML attributes | |
| 18 | +| **Deployment** | Pure ABAP code, no frontend build/deploy, via abapGit | Standard web app deployment, no frontend frameworks needed | |
| 19 | + |
| 20 | + |
| 21 | +## Conclusion |
| 22 | + |
| 23 | +abap2UI5 takes the best of the "HTML Over the Wire" philosophy and applies it to SAP UI5 development. It reduces the overhead of typical SAP frontend architectures by: |
| 24 | +- Keeping all logic and state in ABAP. |
| 25 | +- Avoiding OData, CDS, and separate frontend deployments. |
| 26 | +- Leveraging UI5 XML Views for rendering without losing UI5 flexibility. |
| 27 | + |
| 28 | +For developers familiar with SAP GUI and ALV, abap2UI5 offers a modern yet minimalistic approach to build UI5 applications — fast, backend-driven, and efficient. |
| 29 | + |
| 30 | +## Further Reading |
| 31 | + |
| 32 | +- [abap2UI5 GitHub Repository](https://github.com/abap2UI5/abap2UI5) |
| 33 | +- [htmx Documentation](https://htmx.org/docs/) |
| 34 | +- [Phoenix LiveView Documentation](https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html) |
| 35 | +- [Laravel Livewire Documentation](https://laravel-livewire.com/docs) |
0 commit comments