|
|
| (22 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {{ScoutPage|cat=Concepts}}
| + | The Scout documentation has been moved to https://eclipsescout.github.io/. |
| − | | + | |
| − | 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.
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | == Single form application ==
| + | |
| − | | + | |
| − | As shown in the example screenshot below, form based applications are well suited for smaller and simpler applications.
| + | |
| − | To cover many entities and allow for sophisticated navigation (see example below), table and tree based applications are usually a better match.
| + | |
| − | | + | |
| − | [[Image: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: | + | |
| − | * In the Scout client plugin: A {{ScoutLink|Concepts|Form|form}}, called DesktopForm.
| + | |
| − | * In the Scout server plugin: A {{ScoutLink|Concepts|Process_Service|process service}}, called DesktopProcessService
| + | |
| − | * In the Scout shared plugin: The process interface IDesktopProcessService and the a {{ScoutLink|Concepts|FormData|form data}} (a kind of DTO), called DesktopFormData
| + | |
| − | | + | |
| − | The desktop form is opened on client startup.
| + | |
| − | Before it is displayed in the client application frame, the wiring provided with the single form application fetches data from the Scout server using the desktop process service.
| + | |
| − | | + | |
| − | == Outline based application ==
| + | |
| − | | + | |
| − | [[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 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.
| + | |
| − | | + | |
| − | == Empty application ==
| + | |
| − | | + | |
| − | The empty application templates allows for maximum flexibility.
| + | |
| − | However, the developer needs to know exactely what she/he is doing.
| + | |
| − | | + | |
| − | This type of application correspond to a minimal client server application.
| + | |
| − | * Empty desktop client application frame
| + | |
| − | * No forms in the Scout client
| + | |
| − | * No related form services in the Scout server
| + | |
| − | | + | |
| − | == See also ==
| + | |
| − | * {{ScoutLink|HowTo|Create a new project|How to create a new application}}
| + | |
| − | * {{ScoutLink|Concepts|Desktop|Desktop}}
| + | |
| − | * {{ScoutLink|Concepts|Outline based application|Outline based application}}
| + | |
