todo
- Screen (dashboard) and dashboard elements and in the repo
- Components and layouts Layout container/child relationships and page structure
- Types of component and what they look like
- Containers: areas, forms: is there any difference?
- Fields
- Data components and data views
- forms
- grids
- etc
- Connecting components to data - link out
- finding container (don't use parent because the useless parent field only shows the application)
- Components and layouts in the palette → Themes and palletes
- Responsive design - point to theme 2 pages (can these be generalised)
- Changing design - styles and shared styles.
...
- /wiki/spaces/HELP90/pages/2076246053
- Position, Size and Flow of Layout Components.
- Drag-and-Drop Techniques.
...
Creating Clear Spaces on a Screen - dashboard elements
8.3 or earlier: You can divide up a screen into multiple parts, called dashboard elements, using the Add options. In the repository, you can see the different elements listed under the dahboard.
Areas
Areas are containers
- 8.3 or earlier: Area not bound to data (changing this time)
- card-area (container) - for cards
- form-area - not just for "forms". This area can be backed by data
8.3 or earlier
- Form backed by one stream only
- To show data from another stream
- Card-area (container) - as this can have its own data One card to show the attribute.
Components and layouts
A component can be:
...
Connecting components to data → link
Data components are automatically backed by data.
You can start with data or a compoinent
Backed by
- a stream
- a view - s
- 8.3 or earlier - aa stream plus filters
- 9.0 onwards - a stream, attributes from related streams (see ERDS) plus filters etc.
Finding a Component's Container
| Anchor | ||||
|---|---|---|---|---|
|
...