10,730
edits
Important: Deprecating old WebView — Publish failed error
Resco Platform: Difference between revisions
Jump to navigation
Jump to search
→User interface
| Line 27: | Line 27: | ||
=== User interface === | === User interface === | ||
The user interface of an app is built from '''components''', such as views, forms, dashboards, maps, calendars, etc. An unlimited number can be created. An app's logic can interact with services like email, phone call, bar code, camera, microphone, or GPS. | The user interface of an app is built from '''[[User interface components|components]]''', such as views, forms, dashboards, maps, calendars, etc. An unlimited number can be created. An app's logic can interact with services like email, phone call, bar code, camera, microphone, or GPS. | ||
An '''entity view''' displays a list of items, each representing a single record of an entity. The view filter determines which records. Choosing which entity fields are displayed and in which design is determined by the view-row design. | An '''entity [[view]]''' displays a list of items, each representing a single record of an entity. The view filter determines which records. Choosing which entity fields are displayed and in which design is determined by the view-row design. | ||
Clicking on an item in the item opens the default '''entity form'''. The purpose of entity form is to display and edit a single record. Conceptually, it is a combination of sub-components. | Clicking on an item in the item opens the default '''entity [[form]]'''. The purpose of an entity form is to display and edit a single record. Conceptually, it is a combination of sub-components. | ||
* The main sub-component is the detail: a table of controls bound to entity fields. App chooses the correct control type (numeric vs checkbox) by the type of the field. The selection, position and design of each control | * The main sub-component is the detail: a table of controls bound to entity fields. App chooses the correct control type (numeric vs checkbox) by the type of the field. The selection, position, and design of each control are configurable. | ||
* The second sub-component is an associated view. This component is an entity view, that is pre-filtered by the relationship of the form’s entity and the view’s entity. The purpose is to present records related to the form’s record. | * The second sub-component is an associated view. This component is an entity view, that is pre-filtered by the relationship of the form’s entity and the view’s entity. The purpose is to present records related to the form’s record. | ||
The app recognizes lookup-fields | The app recognizes lookup-fields and allows the user to navigate to the related record by clicking the lookup-control on the entity-form. | ||
When the app starts the first thing the user sees is the [[home screen]]. End each item of the menu can open an entity view, form, calendar, or dashboard. | When the app starts the first thing the user sees is the [[home screen]]. End each item of the menu can open an entity view, form, calendar, or dashboard. | ||