Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Overview/Scout application"
(New page: An application built with Scout is a complete application. Typically it has a UI with perspectives, views, forms and pages. It may also have a back-end part that is running inside an...) |
m (+ScoutPage) |
||
Line 1: | Line 1: | ||
+ | {{ScoutPage|cat=Scout Runtime}} | ||
+ | |||
An application built with [[Scout]] is a complete application. | An application built with [[Scout]] is a complete application. | ||
Typically it has a UI with perspectives, views, forms and pages. | Typically it has a UI with perspectives, views, forms and pages. | ||
Line 14: | Line 16: | ||
* [[Scout_minicrm_Step-by-StepHowTo|Create your first Scout application]] | * [[Scout_minicrm_Step-by-StepHowTo|Create your first Scout application]] | ||
* [[Scout_IMAP_Step-by-StepHowTo|Create your second Scout application]] | * [[Scout_IMAP_Step-by-StepHowTo|Create your second Scout application]] | ||
− | |||
− | |||
− |
Revision as of 03:48, 1 July 2010
The Scout documentation has been moved to https://eclipsescout.github.io/.
An application built with Scout is a complete application. Typically it has a UI with perspectives, views, forms and pages. It may also have a back-end part that is running inside an application server with server-side Equinox.
Examples of such applications are:
- Standalone rich client platforms (Equinox, SWT/Swing)
- SOA/ESB node consisting of J2EE with service registry and web services (Equinox)
- Rich client platforms with a J2EE Backend (Equinox, SWT/Swing)
Scout SDK guides the developer in building Scout based SOA compliant applications.