ViewTemplates and Layouts
ViewTemplates and layouts define the presentation layer of an ADITO View. ViewTemplates determine what a user sees and can interact with; the layout determines how the ViewTemplates and referenced Views are arranged together. This section introduces the available standard components and helps you find the appropriate type for a use case.
For the relationship between Contexts, Entities, Views, and ViewTemplates, see the Entity Model introduction.
How the components work together
A View contains one or more ViewTemplates and can also reference other Views.
Each ViewTemplate represents a predefined client component, such as a table,
card, form, chart, or timeline. Its type defines the available properties and
therefore the data it can display and the interactions it supports. The
layout property of the View combines these components into a coherent screen.
For example, a FilterView can use a GroupLayout to offer a Table and a
TreeTable as selectable representations of the same records. A PreviewView
can combine a Card, a Generic ViewTemplate, and a ScoreCard with a
HeaderFooterLayout.
Choosing a ViewTemplate
Start with the data scope and the primary task:
- For one record, use a focused component such as a
Card,Generic, orPictureViewTemplate. - For a result set or an editable list, use a table, list, tile, or tree component.
- For a business process or direct user interaction, choose an action-oriented component.
- For aggregation, visualization, scheduling, or a specialised content type, use a chart, time-based, or specialised ViewTemplate.
The pages in the following overview describe the intended use and
configuration of each type. The generated data model
reference provides the complete,
type-specific property reference. It includes shared properties such as
title, entityField, and, where applicable, maxDBRow.
Available ViewTemplates
| Area | Use it for | Available ViewTemplates |
|---|---|---|
| Single-record views | Displaying or editing one selected record. | Card, Generic, Picture, ScoreCard, Signature |
| Multi-record views | Browsing, comparing, or editing a set of records. | BasicTable, CardTable, GenericMultiple, MultiEditTable, Table, Tiles, TitledList, Tree and TreeTable |
| Actions and interaction | Guiding users through actions, drop zones, or steps. | ActionList, Actions, DragAndDrop, Stepper |
| Charts and analytics | Presenting aggregated data as charts. | DynamicMultiDataChart, DynamicSingleDataChart, MultiDataChart, SingleDataChart |
| Planning and time-based views | Scheduling, timeline, and Gantt scenarios. | Gantt, ResourceTimeline, Timeline |
| Specialised views | Handling forms, favourites, search, lookups, maps, reports, or embedded web content. | DynamicForm, Favorite, IndexSearch, Lookup, Map, Report, WebContent |
Device and accessibility support
The device and accessibility support matrix records the manually maintained support status for desktop, tablet, mobile, and accessibility requirements.
Layouts
A layout is configured on the View, not on an individual ViewTemplate. It defines the structure, order, and selection mechanism for the View's ViewTemplates and referenced Views, for example as vertical content, a grid, or selectable sections.
See Layouts for the available layout types and their appropriate use.