All Simplifier applications are based on OpenUI5.
|
SAPUI5 and its open-source variant OpenUI5 help you build enterprise-ready Web apps that are responsive to all devices. The JavaScript UI library and development toolkit contains many feature-rich controls and implements the award-winning SAP Fiori user experience. It helps developers ease and speeds up the development of full-blown HTML5 Web applications. |
The Simplifier App Generator generates OpenUI5 applications based on OpenUI5 Controls. Within Simplifier OpenUI5 Controls are represented by Widgets.
User Interface
To create the user interface of Simplifier applications visually the UI Designer is used. In general, OpenUI5 uses pages to represent views within a single-page-app. Within Simplifier UI Designer, pages are represented by screens. Simplifier applications consist of one or more screens and every screen can be populated with widgets.
Application Logic
Within Simplifier application logic is separated by user stories within the Process Dashboard. Every user story contains an isolated part of the overall application logic and can be edited with the Process Designer. The Process Designer is a visual scripting environment to create application logic based on configuration elements. To find out how to use configuration elements see chapter Process Designer.
How OpenUI5 concepts are handled within Simplifier
OpenUI5 |
Simplifier |
Description |
Pages (Views) |
OpenUI5 pages are represented by screens within Simplifier. A screen collects several widgets in a specific order to represent the user interface. |
|
Controls |
OpenUI5 controls are represented by widgets within Simplifier. A widget represents a specific element in the user interface like buttons, checkboxes, tables and input fields. |
|
View Controller |
screen Controller/User Story |
OpenUI5 view controllers are represented by screen controllers/user stories. There is an n:n relation between user stories and controllers. |
Models |
screen Models and variableHolder Model |
Within Simplifier there is a global model named variableHolder and each screen has its own model named by the screenId. |