Chapter 5
Client components

needs text

5.1 Client Model

needs text


PIC

Figure 5.1: A class diagram for the Scout’s client model.


5.2 Splash Screen

needs text

5.3 Login Box

needs text

5.4 Client Session

needs text

5.5 Desktop

needs text

Existing Documentation

5.5.1 Info Dialog

needs text

5.5.2 Toolbar

needs text

Existing Documentation

5.5.3 Status Line

needs text

5.6 Menus

needs text

Existing Documentation

5.7 Outlines

needs text

Existing Documentation

5.8 Tools

needs text

5.9 Forms

needs text

Existing Documentation

* form validation

5.10 Form Fields

needs text

Every Scout form contains one or several form fields. Form fields therefor represent the basic building blocks of a forms content. Depending on their nature, form fields can display information, accept user input or act as container holding inner form fields. As such container fields can hold inner container fields it is possible to create forms that meet compolex requirements.

Existing Documentation

5.10.1 Common Aspects

needs text

Existing Documentation

* model component * ui component * extension point registration

* model * label * value * exec methods * field validation

5.11 Trees

needs text

* tree nodes * tree form * tree field

5.12 Pages

needs text

Existing Documentation

* page with table * page with nodes

5.13 Search Forms

needs text

Existing Documentation

5.14 Tables

needs text

Existing Documentation

* context menues * editable tables * column types

5.14.1 Image Columns

needs text

Existing Documentation

5.14.2 HTML inside Table Cells

needs text

Existing Documentation

5.14.3 Table Status Bar

nees text

Existing Documentation

5.14.4 Injecting Columns at Runtime

needs text

Existing Documentation

5.15 Workflows and Wizards

Needs text

Existing Documentation