Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 53 Next »

This topic is for application designers who want to create screens, add layouts, bind data to components and change styles.

Overview

There are several stages to designing an application, as outlined in Building Applications. An application provides users with one or more screens, which they use to interact with data.

A screen is made up of:

Sections on this page

  • a dashboard: the empty screen and properties that you want to apply to the whole screen
  • optionally, dashboard elements: these divide a dashboard and enable components in different parts of it to be bound to different data
  • layouts: combinations of components, such as areas, fields, labels, cards, grids and charts, grouped together to create parts of the screen. Layouts start with container components:
    • areas: can contain any other component
    • forms: designed to contain fields and their labels
    • card-containers: designed to contain cards
  • data-bound components: some components are designed to display data. These are:
    • graphs, charts and grids, which are based on views. These components display stream-items:
      • either individually, for example in a grid
      • or combined into a chart or graph
    •  form fields and cards: show several data points (attributes) for a selected stream-item: 
      • either in the fields on a form
      • or in a card

You can build up your own layouts from individual components. However, we recommend that you simply use ready-made layouts that you can drag from the palette onto a screen. Some layouts, called tiles, are specifically designed to resize and move components in response to changes in screen size and device form.

Some layouts or components are designed for user interaction, such as buttons. However, you can configure also events, such as user clicks on part of a screen, to trigger actions. For information about configuring user interaction for screens, see 

Binding data to components on a screen requires streams, stream-items and attributes to be present; see the Setting Up Data Relationships and Views topic for details.

This topic explains how to:

Pages in this Topic

Other pages in this topic

  • No labels