Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Scout/Concepts"

(Client)
Line 18: Line 18:
  
 
== Client ==
 
== Client ==
[[Image:Scout Client Concepts.png]]
+
Depending of  {{ScoutLink|Concepts|Type of application|the type of application}}, the client concepts are not equally used.
  
The client typical Eclipse Scout application is composed of {{ScoutLink|Concepts|Outline|Outlines}}. Each outline contains {{ScoutLink|Concepts|Page|pages}} that are represented in a tree ''(on the left)''. A kind of pages are {{ScoutLink|Concepts|TablePage|TablePage}} ''(in red)'' that represent a list of entities (here “''categories''”). A {{ScoutLink|Concepts|SearchForm|SearchForm}} ''(in green)'' can be associated to the TablePage in order to limit the list of entities. In the {{ScoutLink|Concepts|Table|Table}}, a context {{ScoutLink|Concepts|Menu|Menu}} ''(in purple)'' can be added in order to propose some actions on the entity: typically create, modify and delete operations. To create or modify an Entity, a {{ScoutLink|Concepts|Form|Form}}'' (in orange)'' can be used.
+
The {{ScoutLink|Concepts|Desktop|Desktop}} can be considered as the root of the application. It configures the main window.
  
 +
For the user interaction, {{ScoutLink|Concepts|Action|actions}} such as {{ScoutLink|Concepts|Menu|menus}} allows the user to trigger some actions. {{ScoutLink|Concepts|Form|Forms}} and their {{ScoutLink|Concepts|Field|field}} provide some controls to enter some data.
 +
 +
{{ScoutLink|Concepts|Outline|Outlines}} and {{ScoutLink|Concepts|Page|Pages}} are particularly relevant for {{ScoutLink|Concepts|Outline_based_application|outline based application}}.
  
 
== Server ==
 
== Server ==

Revision as of 16:43, 12 September 2011

The Scout documentation has been moved to https://eclipsescout.github.io/.

The Concepts pages define concepts and elements used in the Eclipse Scout Framework.

Plug-ins

Scout Client Shared Server.png

A Scout project is composed of different Eclipse plug-ins. (each plug-in is an Eclipse Project)

The Scout runtime rely on The Scout documentation has been moved to https://eclipsescout.github.io/.. Therefore additional plug-ins are required:

  • SWT UI Plug-In (eg your.application.ui.swt)
  • Swing UI Plug-In (eg your.application.ui.swing)


Client

Depending of The Scout documentation has been moved to https://eclipsescout.github.io/., the client concepts are not equally used.

The The Scout documentation has been moved to https://eclipsescout.github.io/. can be considered as the root of the application. It configures the main window.

For the user interaction, The Scout documentation has been moved to https://eclipsescout.github.io/. such as The Scout documentation has been moved to https://eclipsescout.github.io/. allows the user to trigger some actions. The Scout documentation has been moved to https://eclipsescout.github.io/. and their The Scout documentation has been moved to https://eclipsescout.github.io/. provide some controls to enter some data.

The Scout documentation has been moved to https://eclipsescout.github.io/. and The Scout documentation has been moved to https://eclipsescout.github.io/. are particularly relevant for The Scout documentation has been moved to https://eclipsescout.github.io/..

Server

The server exposes services for the client:


Shared

It contains resources that are required by the Client and the Server: 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/., The Scout documentation has been moved to https://eclipsescout.github.io/., The Scout documentation has been moved to https://eclipsescout.github.io/., Interfaces...


See also

Back to the top