|
|
| Line 1: |
Line 1: |
| − | {| align="right"
| |
| − | | __TOC__
| |
| − | |}
| |
| − |
| |
| | The [http://www.eclipse.org/proposals/scout/ Eclipse Scout] project is a proposed open source project under the Eclipse Technology Project. | | The [http://www.eclipse.org/proposals/scout/ Eclipse Scout] project is a proposed open source project under the Eclipse Technology Project. |
| − |
| |
| − | == 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.
| |
| | | | |
| | == Key Concepts == | | == 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.
| |
| − |
| |
| − | 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, you may write code manually and via click-and-build, doesn't matter
| |
| − | # ...
| |
| − |
| |
| − | == 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
| |
| − |
| |
| − | == A scout form ==
| |
| − | This a simple form with a title and two string fields
| |
| − |
| |
| − | public class PersonForm extends AbstractForm{
| |
| − | //...
| |
| − | }
| |
| − |
| |
| | | | |
| | == How Tos == | | == How Tos == |
