Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
This page is for application designers. It explains how the structure of a screen is made up of layouts and components.
Overview
A screen is made up of components (the smallest building block) and layouts (a group of components) arranged into layers. Components are items such as areas, static text labels and form fields, which display data from a table. Layouts are items such as a Tile Button Bar or TileMulti-component layouts can be simple, such a a label and a field, or more complex parts of a screen with responsive design, these are called tiles. Layouts can also be full screens.
Screen Layers
A typical screen has a layered structure, in which the Layers are one layer is other layers will adapt
Components
These Components are the most basic building blocks that are combined to design a screen.
Components are available from any palette, for example theme . For example, one of the Theme 2.1 they can be found under palettes has the Basic Layouts. For every component you add, you need to give it a name and specify the formatting using the Component properties. It's a good idea to include a meaningful description too.
The basic components are:
Containers | Data Fields | Text Fields | Data Components |
---|---|---|---|
Containers are designed to hold other components | Data fields are designed to display data from an attribute. | Text fields are designed to be labels. | These Data components may not be available directly from on the palette. You can create a data component by dragging a stream onto a dashboardInstead, your application has default components that it uses when you drag a table or attribute onto the screen canvas. PhixFlow prompts you to choose a: |
|
|
|
|
Layouts
Layouts are groups of preconfigured components that have been preconfigured. You can create these yourself by combining and styling components or you can use the pre-built layouts from a palette (recommended). For example, a simple layout is for a tile is illustrated below:
- Tile contains the styles which make the area look lie a tile and controls is an area container with styling to control its size and the layout of its child objectscomponents.
- Header
- is an area which contains
- an
- icon
- a static text text field for the header.
- Body, in the illustration, the body area is empty. This is where you can add data components,
- such as a grid displaying table data, or form fields. The body area has styling to control its size and the layout of its child components. It also has spacing around its edge.
- Footer, area which
- contains a set of buttons
- .
The application user will use the buttons to make changes to data will appear in the body.
Finding Layouts and Components
Anchor | ||||
---|---|---|---|---|
|
It can be very useful to find a layout, component or the items which contains themcontainer. There are two ways to achieve do this:
Using
theLayers
The Layers navigator pane is expandable from the left hand side. Selecting of the screen canvas. Select an item from :
- on the canvas
- to highlight it in the
- Layers pane
- in the Layouts
- pane to highlight it on the canvas.
If the layer section is not visible click
. Insert excerpt _layer_slider _layer_slider nopanel true
Using
findFind in Repository
Right-click any item on an unlocked screen and select
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Tip |
---|
For the selected Layout or Component, To check whether a component is shared with multiple applications, open its properties and check the Parent Details section at the top of the properties tab indicates the , which names the application or package to which it the component belongs. For example a component that is shared between several applications will have has a package as it's parentits parent; see Package. |
Moving
Layouts andComponents
On Screen
Click and hold on a layout or component- Dragging in this way creates a sibling relationship. For example, if you drag ad drop a field on top of another field they appear next to each other.
- Shift-drag creates a parent child relationship, where your dragged item drops into an appropriate container.
In the Repository
Click and drag them in theSpecial Cases
Components can be marked with Prevent Dragging, this stops an item from being moved on a screen. It is however still moveable within the repository. This setting can be found in the items Properties → Design tab → Position Settings section.
In the example below we may want to fix the header in a set location, and therefore set it to Prevent Dragging.
Composite Component
Form Fields are composite Components
In the example below a tile is being dragged onto a screen from the palette. The tile container is highlighted in blue as it is the preferred parent of the tile.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|