Difference between revisions of "Scout/Overview/Scout application"
Dev.jmini.fr (Talk | contribs) m (+ScoutPage) |
|||
| Line 1: | Line 1: | ||
| − | {{ScoutPage|cat= | + | {{ScoutPage|cat=Overview}} |
An application built with [[Scout]] is a complete application. | An application built with [[Scout]] is a complete application. | ||
| Line 10: | Line 10: | ||
* Rich client platforms with a J2EE Backend (Equinox, SWT/Swing) | * Rich client platforms with a J2EE Backend (Equinox, SWT/Swing) | ||
| − | + | {{ScoutLink|SDK|name=Scoud SDK}} guides the developer in building Scout based SOA compliant applications. | |
== See also == | == See also == | ||
| − | * | + | * {{ScoutLink|Tutorial|Project From Existing Workspace|Download an existing Scout application}} |
| − | * | + | * {{ScoutLink|Tutorial|Minicrm Step-by-Step|Create your first Scout application}} |
| − | * | + | * {{ScoutLink|Tutorial|IMAP Step-by-Step|Create your second Scout application}} |
Revision as of 04:25, 8 July 2010
| Scout |
| Wiki Home |
| Website |
| Download • Git |
| Community |
| Forums • Blog • Twitter • G+ |
| Bugzilla |
| Bugzilla |
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)
Scoud SDK guides the developer in building Scout based SOA compliant applications.