Skip to content

Latest commit

 

History

History
45 lines (30 loc) · 3.26 KB

Model_View_Controller_MVC_91f2334.md

File metadata and controls

45 lines (30 loc) · 3.26 KB
loio
91f233476f4d1014b6dd926db0e91070

view on: demo kit nightly build | demo kit latest release

Model View Controller (MVC)

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

Model, view, and controller are assigned the following roles:

  • The view is responsible for defining and rendering the UI.
  • The model manages the application data.
  • The controller reacts to view events and user interaction by modifying the view and model.

UI5 separates data model, UI view, and application logic (controller).

The purpose of data binding in the UI is to separate the definition of the user interface (view), the data visualized by the application (model), and the code for the business logic for processing the data (controller). The separation has the following advantages: It provides better readability, maintainability, and extensibility and it allows you to change the view without touching the underlying business logic and to define several views of the same data.

Views and controllers 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 OpenUI5 control and can have or inherit a OpenUI5 model.

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

  • Models
    A model in the Model View Controller concept holds the data and provides methods to retrieve the data from the database and to set and update data.
  • Views
    The view in the Model-View-Controller (MVC) concept is responsible for defining and rendering the UI. OpenUI5 supports predefined view types.
  • Controller
    A controller contains methods that define how models and views interact.
  • Support for Unique IDs
    Stable IDs are used to identify and modify the controls within the controller during runtime. However, if you reuse or nest these views, these stable IDs are no longer unique. To avoid ambiguity, each view adds its own ID as prefix to all its child controls.