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.
Scout/Overview/Why You Should Use Scout
< Scout | Overview
Revision as of 10:43, 16 March 2010 by Bsh.bsiag.com (Talk | contribs) (New page: 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...)
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 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