Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Concepts/Type of application"
(→Empty application) |
(→Single form application) |
||
| Line 15: | Line 15: | ||
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. | 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 | + | 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 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. | ||
With this type of application, there is no default support for outlines and pages. | With this type of application, there is no default support for outlines and pages. | ||
Revision as of 12:02, 18 September 2013
The Scout documentation has been moved to https://eclipsescout.github.io/.
During the creation of The Scout documentation has been moved to https://eclipsescout.github.io/., 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 a minimal client server application.
- Empty desktop client application frame
- No forms in the Scout client
- No related form services in the Scout server
Single form application
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 The Scout documentation has been moved to https://eclipsescout.github.io/., called DesktopForm.
- In the Scout server plugin: A The Scout documentation has been moved to https://eclipsescout.github.io/., called DesktopProcessService
- In the Scout shared plugin: The process interface IDesktopProcessService and the a 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.
With this type of application, there is no default support for outlines and pages.
Outline based application
The Scout documentation has been moved to https://eclipsescout.github.io/. is the most complete type of application. It is suitable if you want to represent The Scout documentation has been moved to https://eclipsescout.github.io/. and their The Scout documentation has been moved to https://eclipsescout.github.io/. 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
- The Scout documentation has been moved to https://eclipsescout.github.io/.
- The Scout documentation has been moved to https://eclipsescout.github.io/.
- The Scout documentation has been moved to https://eclipsescout.github.io/.