Jump to: navigation, search

Difference between revisions of "Scout/Concepts"

(Samples)
(new version of the page (old content is available on other pages))
Line 2: Line 2:
 
{{ScoutPage|cat=Concepts}}
 
{{ScoutPage|cat=Concepts}}
  
{| class="FCK__ShowTableBorders" align="top"
+
The Concepts pages define concepts and elements used in the Eclipse Scout Framework.
|-
+
| __TOC__
+
|}
+
  
= Scout =
+
== Plug-ins ==
Scout is the base of applications that may be developed with or without the Scout SDK. As Scout is written in pure Java/J2EE and satisfies the OSGi paradigm, integration of 3rd party libraries or applications is fully supported. The Scout runtime both provides a large amount of reusable functionality and a library of abstract UI component models.  
+
[[Image:Scout Client Shared Server.png]]
  
The extension point registry is reused to define Scouts extension points. An Eclipse compliant extension point defines the UI representation of every component model. This simplifies adding and changing of specific component representations as well as the application representation. With a Swing and a SWT/JFace representation Scout already provides two UI implementations.
+
A Scout project is composed of different Eclipse plug-ins. (each plug-in is an Eclipse Project)
 +
* {{ScoutLink|Concepts|Client Plug-In|Client Plug-In}} (eg <code>your.application.client</code>)
 +
* {{ScoutLink|Concepts|Shared Plug-In|Shared Plug-In}} (eg <code>your.application.shared</code>)
 +
* {{ScoutLink|Concepts|Server Plug-In|Server Plug-In}} (eg <code>your.application.server</code>)
  
[[Image:Scout_architecture_overview.png]]
+
The Scout runtime rely on {{ScoutLink|Concepts|Separation UI and GUI|separation of UI and GUI}}. Therefore additional plug-ins are required:
 +
* SWT UI Plug-In (eg <code>your.application.ui.swt</code>)
 +
* Swing UI Plug-In (eg <code>your.application.ui.swing</code>)
  
= Client Component Modell =
+
== Client ==
[[Image:client_components.png]]
+
{{note|TODO|Main concepts in the client}}
== Client Session ==
+
The client session is the main entry point for client-server communication.
+
  
== Desktop ==
+
== Server ==
The desktop is the entry point of every Scout client application. It can (may) consist of top-level menus, active message box stack, set of available outline, active outline, active tableview, active detail form, active search form, form stack (swing: dialogs on desktop as JInternalFrames; eclipse: editors or views), dialog stack of modal and non-modal dialogs (swing: dialogs as JDialog, JFrame; eclipse: dialogs in a new Shell).
+
{{note|TODO|Main concepts in the Server}}
  
== Menu ==
+
== Shared ==
The menu component will include all links, functionalities, etc... available within the application.
+
{{note|TODO|Main concepts in the Shared}}
  
== Tool ==
+
== See also ==
Tool component will be used for grouping or dividing different views. This can be used for building business views on datas or just structuring your own application.
+
*[[:Category:Scout_Concepts|All Eclipse Scout Concepts]]
 
+
== Outline==
+
Typically a Desktop holds multiple outlines. They represent different entry points for the navigation within the application. For every outline a tree is available which allows navigating within the application.
+
== Form ==
+
A form is both a model structure of a ui concept known as dialog or view and also a model of a wizard page. Wizard buttons are added automatically to the main box if missing.
+
=== Form fields ===
+
Form fields are the basic elements for user inputs fiels within a form. Examples are:
+
* TextField
+
* SmartField
+
* NumberField
+
* DateField
+
* FileChooser
+
* ListBox
+
* TreeBox
+
* CheckBox
+
* RadioButton
+
* ToogleButton
+
 
+
Futhermore there exists composites fields like:
+
* GroupBox
+
* TabBox
+
* SequenceBox
+
* SnapBox
+
* RangeBox
+
* RadioButtonGroupBox
+
 
+
 
+
=== Samples ===
+
* {{ScoutLink|Concepts|Forms/Example|name=Scout form}}
+
 
+
== Wizard ==
+
Wizards will support a user to work in a process driven approach on a task.
+

Revision as of 11:55, 5 June 2011


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitter
Bugzilla
Bugzilla


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 separation of UI and GUI. 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

Note.png
TODO
Main concepts in the client


Server

Note.png
TODO
Main concepts in the Server


Shared

Note.png
TODO
Main concepts in the Shared


See also