SAP UI5 Online Training

02:31 | Labels: SAP-UI5

SAP UI Development Toolkit for HTML5 (SAPUI5) is a user interface technology that is used to build and adapt client applications based on SAP NetWeaver Neo. The SAPUI5 runtime is a client-side HTML5 rendering library with a large set of RIA-like standard and extension controls based on JavaScript (JS), and a lightweight programming model.

Application Programming in SAP UI5:

Application UI5
Bootstrap core controls

SAP UI5 Developer studio:

Take a look at a sample application options and design tips to guide development with SAPUI5.

Modularization and resource handling for SAP UI5 :

SAP UI5 framework has built-in support and modularzing . comprehensive javascript applications. sap ui5 localization & modularization .

MVC Architecture of SAPUI5:

This model gives mainly about MVC architecture of SAP UI5 . The model-vie-controller separates the modelling.

Three different device input classes:

1. The View

2. The Controllers

3. The Model

Data Binding in SAP UI5:

SAP UI uses the data binding to bind ui controls to a data source that holds the application data. model binding model with ui element types of bindings in SAP UI5 Odata styling and theming adjusting styles and themes

Extending SAP ui5:

Extended of SAP UI5 and including Notepad controls.

MVC Architecture in SAP UI5 :

The Model View Controller (MVC) is used in SAPUI5 to separate the representation of information from the user interaction. This facilitates will be development and the changing of parts independently.

Model, view and controller are assigned following roles:

The view is responsible for defining and rendering the UI.

The model will manages the application data.

The controller reacts with view events and user interaction by modifying the view and model.

The purpose of data binding in UI is to separate the definition of the user interface (view), the data visualized by the application (model), and the code will be used for the business logic for processing the data (controller).

The separation has following the advantages: It provides readability, maintainability, and extensibility and it will be used to change the view without touching they underlying business logic and to define the several views of the same data.

Views and controllers will often form a 1:1 relationship, but it is also possible to have controllers without a UI, these controllers are called application controllers. It is also possible to create views without controllers. From a technical position, a view is a SAPUI5 control and can have or inherit a SAPUI5 model.

View and controller represent reusable units, and distributed development is highly supported.