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.
Difference between revisions of "Scout"
(→My first application) |
(→My first application) |
||
| Line 60: | Line 60: | ||
#com.example.mail.shared.core | #com.example.mail.shared.core | ||
#com.example.mail.server.core | #com.example.mail.server.core | ||
| − | [[ | + | |
| + | [[Step-by-Step HowTo]] | ||
== Screens == | == Screens == | ||
Revision as of 05:30, 16 March 2010
| Eclipse Scout | |
| Website | |
| [ Download] | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source |
The Eclipse Scout project is a proposed open source project under the Eclipse Technology Project.
Please note that these pages are work in progress and still far from complete.
What is it
The eclipse Scout Plug-Ins are used to build applications based on eclipse and equinox. These may be standalone apps, client/server apps, headless apps on server-side equinox etc.
Eclipse Scout consists of a runtime and an SDK part. The runtime part consists of approx. five Plug-Ins, the SDK consists of approx. three Plug-Ins.
The runtime is purely based on equinox, and eclipse. The SDK part is an extension to JDT and PDE with a complete perspective for easy click-and-build of a complete application.
Read the more detailed Scout Overview.
Key Concepts
An applications built with eclipse Scout typically has a UI with perspectives, views, forms and pages. It may also have a back-end part that is running in an application server with server-side equinox. Perspectives, views, forms and pages are not limited to SWT, Scout supports complete GUI pluggability and also supports Swing of the box.
With eclipse Scout you have
- Separation of UI (user interface layer) and GUI (graphical user interface). SWT and Swing GUI factory
- Complete workspace overview, multiple Plug-Ins participating to the same application are visualized with their high-level dependencies
- Much convenience and support in writing only the code you want to write when for example writing a new form with many sections and fields
- Automatic nls support as-you-type
- Soap-based remote service tunnel for hi-speed service remoting to a eclipse server-side application
- Extension point for declaring OSGi services and remote service proxies
- Extension point for UI component to gui widget mapping
- Complete abstration layer for desktop (workbench), outlines (perspectives), forms (views, dialogs) and fields
- Configurable code
- Template concept for creating abstract class libraries
- Strong typed code, minimized "string binding" and therefore best support by PDE and JDT
- No meta data and no one-way code genration; everything is in the Java code you write. If you prefer to write code manually, or via click-and-build, doesn't matter
Architecture
- Overview
- Client
- Server
- Development Environement
My first application
Easiest way to begin is creating a new eclipse Scout project group and choosing the mail sample application. A project group is a set of Plug-Ins that make up your application. Project name: com.example.mail Project parts: client, server, SWT UI This will create the Plug-Ins (listed by layer)
- com.example.mail.ui.swt.core
- com.example.mail.client.core
- com.example.mail.shared.core
- com.example.mail.server.core
Screens