Skip to main content
Jump to: navigation, search

Scout/Concepts/Type of application

< Scout‎ | Concepts
Revision as of 15:30, 12 September 2011 by (Talk | contribs)

Wiki Home

During the creation of a new Scout Project, it is possible to chose the type of Application that should be created. This page gives an overview of the different type.

There is no big differences between the proposed type. The SDK will use different code templates, to create the application. The main differences are in the Desktop class: the implementation of Opened event is not the same. There is nothing you can't program on your own if you change your mind afterward.

Empty application

This type of application correspond to the minimal application. No additional code is generated.

Single form application

Scout single form application.png

In this type of application, the main windows display a form. In this example (Swing, Nimbus look and feel, Windows), the menu bar is displayed in this main window on top of the main form.

The SDK add add a form, called DesktopForm. This form comes with a process service (DesktopProcessService) and a form handler (DisplayFormHandler).

With this type of application, there is no default support for outlines and pages. For example, if a page needs to be displayed, one of the forms need to provide a PageField to do so.

Outline based application

Scout outline based application.png

Outline based application is the most complete type of application. It is suitable if you want to represent outlines and their pages in the main window. In this example (Swing, Nimbus look and feel, Windows) the main window provide: the menu bar, a way to switch between the Outlines attached to the desktop, and a representation of the active outline: on the left its page tree and on the right the selected page.

The SDK prepare the main window in the Opened of the Desktop. A good start is to add a first outline to the application.

See also

Back to the top