| loio |
|---|
| 9ef211e569ed4f819af904ba360ea7f6 |
view on: demo kit nightly build | demo kit latest release
List of terms used in OpenUI5.
|
Term |
Meaning |
Source/Comments |
Link |
|---|---|---|---|
|
SAPUI5 ABAP repository |
Used to store SAPUI5 apps, components, and libraries; based on the Business Server Page (BSP) repository of the ABAP server. A SAPUI5 application stored in the ABAP repository can be deployed and executed in a browser directly. It is connected to the ABAP transport system. |
SAPUI5 only |
|
|
aggregation |
An aggregation is a special relation between two UI element types. It is used to define the parent-child relationship within the tree structure. The parent end of the aggregation has cardinality 0..1, while the child end may have 0..1 or 0..*. The element's API offers convenient and consistent methods to deal with aggregations (e.g. to get, set, or remove target elements). Examples are table rows and cells, or the content of a table cell. |
SAPUI5/OpenUI5 |
|
|
association |
An association is a type of relation between two UI element types which is independent of the parent-child relationship within the tree structure. Directed outgoing associations to a target of cardinality 0..1 are supported. They represent a loose coupling only and are thus implemented by storing the target element instance's ID. The most prominent example is the association between a label and its field. |
SAPUI5/OpenUI5 |
|
|
ARIA |
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. (Quote from w3c.org) |
|
|
|
asynchronous (async) processing |
In contrast to synchronous processing this processing mode does not keep the browser thread busy but does the processing in the background and continues with the next task. Code can be executed asynchronously and a callback function is triggered when a certain condition is met. Similarly, a file can be loaded asynchronously. Asynchronous processing is highly recommended for performance reasons and to not freeze the UI. |
SAPUI5/OpenUI5 |
|
|
asynchronous module definition (AMD) |
A mechanism for defining a module in a way that modules and their dependencies can be loaded asynchronously. |
|
|
|
asynchronous action |
An asynchronous action is one that the backend can execute sometime after the users initially trigger it. The users should then be allowed to work on the UI without any interruption to their flow. |
SAP Fiori elements |
|
|
bootstrap |
To use the OpenUI5 features in your web page, you have to load and initialize – or "bootstrap" – the OpenUI5 runtime in your HTML page. |
SAPUI5/OpenUI5 |
|
|
BPMN |
A standard Business Process Model and Notation (BPMN) will provide businesses with the capability of understanding their internal business procedures in a graphical notation and will give organizations the ability to communicate these procedures in a standard manner. Furthermore, the graphical notation will facilitate the understanding of the performance collaborations and business transactions between the organizations. |
|
|
|
(application) cache buster |
A cache buster allows the application to notify the browser to refresh the resources only when the application resources have been changed. Otherwise the resources can always be fetched from the browser's cache. The application cache buster is a special mechanism to extend this function to application resources |
SAPUI5/OpenUI5 |
|
|
cache busting: single application resources |
Cache busting on the level of a single app, component, or library in the SAPUI5 ABAP repository |
SAPUI5 only |
|
|
cache busting; multiple application resources |
Cache busting on the level of multiple apps, components, or libraries in the SAPUI5 ABAP repository |
SAPUI5 only |
|
|
clickjacking |
Clickjacking, or UI redressing, tricks the user into triggering actions within an application by redirecting clicks. This is done, for example, by using an invisible iFrame which is positioned above a fake UI. When the user clicks on something on the fake UI, the content of the invisible iFrame handles the click. |
SAPUI5/OpenUI5 |
|
|
composite control |
Composite controls are intended for reuse within control development and allow you to include existing controls in a complex control. |
SAPUI5/OpenUI5 |
|
|
content density |
The devices used to run apps that are developed with SAPUI5 run on various different operating systems and have very different screen sizes. SAPUI5 contains different content densities for certain controls that allow your app to adapt to the device in question, allowing you to display larger controls for touch-enabled devices and a smaller, more compact design for devices that are operated by mouse. |
SAPUI5/OpenUI5 |
|
|
control |
UI elements that can be used independently. From a developer's point of view, a control (e.g. |
SAPUI5/OpenUI5 |
|
|
controller |
An application unit containing the active part of the application. It is the logical interface between a model and a view, and corresponds to the model view controller (MVC) concept. |
SAPUI5/OpenUI5 |
|
|
Cross-Site Scripting (XSS) |
Cross-site scripting is about injecting script code into a web page, which is then executed in the context of the page. Therefore it can access any information which is currently displayed on the screen. Additionally, XSS attacks can access session information contained in cookies, or send new requests to the server within the current session, or even try to exploit browser vulnerabilities to get full access to the machine that the browser is running on. |
SAPUI5/OpenUI5 |
|
|
data binding |
A technique that binds two data sources together in order to keep them in sync. All changes in one data source are automatically reflected in the other; the involved layers are the view and the model. |
SAPUI5/OpenUI5 |
|
|
data type |
Data types are first-class entities in the meta model. This allows reuse of types across libraries and extensibility of the type system. The core library (technically, this is the |
SAPUI5/OpenUI5 |
|
|
Demo Kit |
The Demo Kit is the OpenUI5 software development kit (SDK). The Demo Kit is your one-stop shop for all information about OpenUI5: documentation, API reference, samples, demo apps. |
SAPUI5/OpenUI5 |
|
|
diagnostics |
A diagnostics window is available in OpenUI5 applications. To open it, use the following shortcut: [Ctrl] + [Shift] + [Alt] /[Option][S] |
SAPUI5/OpenUI5 |
|
|
distribution layer |
Contains the control libraries and theme libraries; also known as SAPUI5 distribution layer. |
SAPUI5 only |
|
|
Document Object Model (DOM) |
The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page. (Quote from w3c.org) |
|
|
|
element |
A (UI) element is the basic building block of our user interfaces; it is a reusable entity with properties, events, methods, and relations. The most important relations are aggregations to other UI elements, and in this way a tree structure of elements can be created. |
SAPUI5/OpenUI5 |
|
|
entity |
In an OData definition of a data model, an entity corresponds to a business object in an application. The data model also defines the association among the entity types. For example, for a sales order processing application, the data model can define sales order as an entity and sales order item as its child entity. In the application interface, this association allows the users to navigate from the sales order to the sales order item. |
SAP Fiori elements |
|
|
SAP Fiori launchpad |
SAP Fiori launchpad is a shell that hosts SAP Fiori apps, and provides the apps with services such as navigation, personalization, embedded support, and application configuration. |
SAP Fiori |
|
|
event |
An event has a name as well as any number of parameters. The element's API offers support to manage event subscriptions. |
SAPUI5/OpenUI5 |
|
|
JAWS Screen Reader |
JAWS, Job Access With Speech, is the world's most popular screen reader, developed for computer users whose vision loss prevents them from seeing screen content or navigating with a mouse. JAWS provides speech and Braille output for the most popular computer applications on your PC. |
Freedom Scientific |
|
|
jQuery |
JavaScript library that is packaged with OpenUI5. jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers. (Quote from jquery.com) |
|
|
|
key annotations |
Key annotations are the most important annotations that defines the rendering or behavior of a control. For example:
|
SAP Fiori elements |
|
|
layout management |
Layout Management refers to how the information in the object page is displayed on the UI. The SAPUI5 |
SAP Fiori elements |
|
|
library |
The top-level structural unit is called a library. Libraries are the main artifacts in the extensibility concept. They bundle a set of controls and related types and make them consumable by Web applications. There are predefined and standard libraries, like |
SAPUI5/OpenUI5 |
|
|
main entity |
Main entity refers to the entry entity that holds the information displayed in the SAP Fiori elements template. For example, in a typical Manage Sales Order application, the |
SAP Fiori elements |
|
|
mock server |
A mock server is a mocking framework for HTTP and HTTPS that is used to simplify integration testing and to decouple development teams by allowing them to develop against a service that is incomplete or unstable. The mock server included with OpenUI5 mimics OData V2 back-end calls. Mock server functionality for OData V4 is included with CAP Node.js. |
SAPUI5/OpenUI5 |
|
|
model |
Data provider for the application where the model instance is assigned to the UI and the controls are bound to the model. Various model types are available; the model type used depends on the data format available on the server side. |
SAPUI5/OpenUI5 |
|
|
MVC concept |
A UI programming model that separates the layout (view) from the content (model) and the behavior (controller). The MVC concept is used by the framework to model the architecture of the applications. |
SAPUI5/OpenUI5 |
|
|
navigation entity |
Navigation entity refers to the other entities associated with the given entity set. The associated entity has more detailed information about the objects associated with the main object. For example, the |
SAP Fiori elements |
|
|
notepad control |
A control that is defined on the fly without a library definition or running generation steps. |
SAPUI5/OpenUI5 |
|
|
OData |
OData (Open Data Protocol) is a standard protocol that defines best practices for building and consuming an interface to backend systems over the web. |
SAP Fiori elements |
|
|
OData model |
A model implementation for the Open Data (OData) Web Protocol format. |
SAPUI5/OpenUI5 |
|
|
OPA5 |
OPA5 is an API for OpenUI5 controls. It hides asynchronicity and eases access to OpenUI5 elements. This makes OPA especially helpful for testing user interactions, integration with OpenUI5, navigation, and data binding. |
SAPUI5/OpenUI5 |
|
|
property |
A property has a name and an associated data type. It has a well-defined default value expressed as a literal of that data type. Properties are accessible to application code via the element's API as getters and setters, but are also used by a control's renderer in a read-only way. |
SAPUI5/OpenUI5 |
|
|
SAPUI5 repository upload and download reports |
Alternative for the team repository provider, with similar functionality. |
SAPUI5 only |
|
|
right-to-left (RTL) text directionality |
The |
|
|
|
resource model |
Used to bind texts of a control to language-dependent resource bundle properties. |
SAPUI5/OpenUI5 |
|
|
service |
A service is code that delivers one or more functionalities or capabilities on the backend system, such as, the retrieval of data or execution of a series of actions. The code can be reused for various purposes by different client applications. |
SAP Fiori elements |
|
|
single SAPUI5 repository |
The SAPUI5 ABAP repository consists of n single SAPUI5 repositories, each represented by an individual BSP application (with specific characteristics) in the BSP repository. |
SAPUI5 only |
|
|
SAP Fiori elements |
App developers can use SAP Fiori elements to create SAP Fiori applications based on OData services and annotations requiring no JavaScript UI coding. An app based on SAP Fiori elements uses predefined template views and controllers that are provided centrally, so no application-specific view instances are required. The SAPUI5 runtime interprets metadata and annotations of the underlying OData service and creates the corresponding views for the SAP Fiori app at startup. The predefined view templates and controllers ensure UI design consistency across similar apps. Additionally, the metadata-driven development model significantly reduces the amount of frontend code per app, so the developer can focus on the business logic. SAP Fiori elements comprise templates for "List Report", "Object Page", and "Overview Page". |
SAPUI5 only |
|
|
scalable vector graphics (SVG) |
SVG is a markup language for describing two-dimensional graphics applications and images, and a set of related graphics script interfaces (Quote from w3c.org) |
|
|
|
synchronous (sync) processing |
Synchronous processing keeps the current browser thread until the task is finished. The UI is not updated and no other tasks can be done in parallel. Consider using asynchronous processing for loading files and executing long-running code. |
SAPUI5/OpenUI5 |
|
|
synchronous action |
A synchronous action is one that the backend executes immediately after the user triggers it. Until the execution is complete, the user is blocked from performing any other actions on the UI. |
SAP Fiori elements |
|
|
SAPUI5 text repository |
Part of the SAPUI5 ABAP repository; only to be used as a fallback mechanism if translation using properties files is not possible |
SAPUI5 only |
|
|
view |
An application unit containing the control definitions for the user interface layer in the application, or in other words: defines how the user interface looks like. |
SAPUI5/OpenUI5 |
|
|
wdi5 |
It is Webdriver.IO service, designed to run cross-platform end-to-end tests on a OpenUI5 applications, with selectors compatible to OPA5. |
SAPUI5/OpenUI5 |