Difference between revisions of "Scout/Concepts"
Revision as of 05:21, 8 July 2010
|Download • Git|
|Forums • Blog • Twitter • G+|
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.
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.
Client Component Modell
The client session is the main entry point for client-server communication.
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).
The menu component will include all links, functionalities, etc... available within the application.
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.
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.
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 are the basic elements for user inputs fiels within a form. Examples are:
Futhermore there exists composites fields like:
Wizards will support a user to work in a process driven approach on a task.