User interface components: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Academy|33|User Interface}} | {{Academy|33|User Interface}} | ||
{{Template:UI Components TOC}} | {{Template:UI Components TOC}} | ||
The user interface of [[Resco mobile apps]] is built from components like views, forms, dashboards, maps, calendars. An unlimited number can be created. The app’s logic can interact with any of the services like sending email, starting a phone call, scanning a barcode, recording audio, or acquiring GPS position. | |||
; View | ; View | ||
| Line 8: | Line 8: | ||
; Form | ; Form | ||
The purpose of entity '''form''' is to view and edit a single record. Conceptually it is a combination of sub-components. | The purpose of entity '''form''' is to view 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 is configurable. | * 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 is 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 app recognizes lookup | * 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 and allows the user to navigate to the related record by clicking the lookup-control on the entity-form. | ||
; Home screen | ; Home screen | ||
When the app starts, the first thing the user sees is the '''home screen''' with a menu. 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''' with a menu. End each item of the menu can open an entity view, form, calendar, or dashboard. | ||
[[Category:Core concepts]] | [[Category:Core concepts]] | ||
Revision as of 06:30, 24 September 2020
The user interface of Resco mobile apps is built from components like views, forms, dashboards, maps, calendars. An unlimited number can be created. The app’s logic can interact with any of the services like sending email, starting a phone call, scanning a barcode, recording audio, or acquiring GPS position.
- View
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 a view list item opens the default entity form.
- Form
The purpose of entity form is to view 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 is 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 app recognizes lookup fields and allows the user to navigate to the related record by clicking the lookup-control on the entity-form.
- Home screen
When the app starts, the first thing the user sees is the home screen with a menu. End each item of the menu can open an entity view, form, calendar, or dashboard.