Jump to: navigation, search

Scout/Overview/Why You Should Use Scout


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitter
Bugzilla
Bugzilla


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:

  1. Separation of UI (user interface layer) and GUI (graphical user interface). SWT and Swing GUI factory
  2. Complete workspace overview, multiple Plugins participating to the same application are visualized with their high-level dependencies
  3. 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
  4. Automatic NLS support as-you-type
  5. Soap-based remote service tunnel for hi-speed service remoting to a Eclipse server-side application
  6. Extension point for declaring OSGi services and remote service proxies
  7. Extension point for UI component to gui widget mapping
  8. Complete abstration layer for desktop (workbench), outlines (perspectives), forms (views, dialogs) and fields
  9. Configurable code
  10. Template concept for creating abstract class libraries
  11. Strong typed code, minimized "string binding" and therefore best support by PDE and JDT
  12. No meta data and no one-way code generation; everything is in the Java code you write. If you prefer to write code manually, or via click-and-build, doesn't matter