Skip to main content
Jump to: navigation, search

Difference between revisions of "Scout/Concepts/Type of application"

Line 1: Line 1:
 
{{ScoutPage|cat=Concepts}}
 
{{ScoutPage|cat=Concepts}}
  
During the creation of  {{ScoutLink|HowTo|Create_a_new_project|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.
+
During the creation of  {{ScoutLink|HowTo|Create_a_new_project|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 types.
 
+
There is no big differences between the proposed type. The {{ScoutLink|SDK|name=SDK}} will use different code templates, to create the application. The main differences are in the Desktop class: the implementation of {{ScoutEvent|Opened}} event is not the same. There is nothing you can't program on your own if you change your mind afterward.
+
  
 
== Empty application ==
 
== Empty application ==
Line 13: Line 11:
 
[[Image:Scout single form application.png]]
 
[[Image: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.
+
In this type of application, the main window displays 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 {{ScoutLink|Concepts|Form|form}}, called DesktopForm. This form comes with a {{ScoutLink|Concepts|Process_Service|process service}} (DesktopProcessService) and a {{ScoutLink|Concepts|Form Handler|form handler}} (DisplayFormHandler).
+
The SDK creates a {{ScoutLink|Concepts|Form|form}}, called DesktopForm. This form comes with a {{ScoutLink|Concepts|Process_Service|process service}} (DesktopProcessService) and a {{ScoutLink|Concepts|Form Handler|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.
+
  
 +
With this type of application, there is no default support for outlines and pages.
  
 
== Outline based application ==
 
== Outline based application ==
Line 24: Line 21:
 
[[Image:Scout outline based application.png]]
 
[[Image:Scout outline based application.png]]
  
{{ScoutLink|Concepts|Outline based application|Outline based application}} is the most complete type of application. It is suitable if you want to represent {{ScoutLink|Concepts|Outline|outlines}} and their {{ScoutLink|Concepts|Page|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.
+
{{ScoutLink|Concepts|Outline based application|Outline based application}} is the most complete type of application. It is suitable if you want to represent {{ScoutLink|Concepts|Outline|outlines}} and their {{ScoutLink|Concepts|Page|pages}} in the main window. In this example (Swing, Nimbus look and feel, Windows) the main window provides: the menu bar, a way to switch between the Outlines attached to the desktop, and a representation of the active outline: on the left hand side the page tree and on the right the selected page.
 
+
The SDK prepare the main window in the {{ScoutEvent|Opened}} of the Desktop. A good start is to add a first outline to the application.
+
  
 
== See also ==
 
== See also ==

Revision as of 12:34, 4 May 2012


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitterG+
Bugzilla
Bugzilla


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 types.

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 window displays 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 creates 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.

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 provides: the menu bar, a way to switch between the Outlines attached to the desktop, and a representation of the active outline: on the left hand side the page tree and on the right the selected page.

See also

Back to the top