Layouts
A layout is a property of a View. It determines how the View's ViewTemplates and referenced Views are arranged, selected, and kept visible in the client. Layouts therefore define the structure of a View; the individual ViewTemplates define its content and interaction.
The standard layouts cover linear, grid-based, selectable, header-and-footer, and master-detail structures. This overview helps you select the structure that matches the relationship between the contents of a View.
How layouts and ViewTemplates work together
A View can contain ViewTemplates, references to other Views, or both. The
layout controls their arrangement; it does not determine which EntityFields a
ViewTemplate displays. For example, a GroupLayout can make a Table and a
TreeTable selectable alternatives, while a HeaderFooterLayout can keep a
Card above the remaining content of a PreviewView.
Use a layout when the View contains more than one component or when its
components need a defined relationship. For a single ViewTemplate or referenced
View, NoneLayout is usually sufficient.
Choosing a layout
| Structure required in the View | Suitable layout | Use it when |
|---|---|---|
| One component without additional structure | NoneLayout | The View contains exactly one ViewTemplate or one referenced View. |
| A linear sequence of components | BoxLayout | Components should be arranged vertically or horizontally in a defined order. |
| Several components in rows and columns | GridLayout | The spatial arrangement of several components is important, especially on larger screens. |
| Alternative representations of the same content | GroupLayout | Users should select one of several Views or ViewTemplates, such as a table or timeline. |
| A section with an optional collapsible header | DrawerLayout | Content should remain grouped and users may hide it when it is not needed. |
| Persistent content above and below a main area | HeaderFooterLayout | A header and/or footer must remain visible while the middle area contains the main content. |
| A selection or preview with dependent detail areas | MasterDetailLayout | A master View controls one or more related detail Views, as in a typical MainView. |
Each layout page describes its behaviour, layout-specific properties, and examples. For the component types that a layout can arrange, see the ViewTemplates overview.