|
|
(2 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | {{ScoutPage|cat=Overview}}
| + | The Scout documentation has been moved to https://eclipsescout.github.io/. |
− | | + | |
− | An application built with Scout typically 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. Perspectives, views, forms and pages are not limited to SWT - Scout supports complete GUI pluggability and also supports Swing out of the box.
| + | |
− | | + | |
− | With Scout you have:
| + | |
− | | + | |
− | #Separation of UI (user interface layer) and GUI (graphical user interface). SWT and Swing GUI factory
| + | |
− | #Complete workspace overview, multiple Plugins 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
| + | |
Latest revision as of 06:19, 19 March 2024
The Scout documentation has been moved to https://eclipsescout.github.io/.