Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Scout/SDK/Default Super Classes Preference Page

< Scout‎ | SDK
Revision as of 01:44, 16 July 2014 by (Talk | contribs) (Description)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Wiki Home

One of the Scout Preference Pages.


Default Super Classes Preference Page.png


Since Scout 3.9 it is possible to configure the super classes that should be used for each object type by default for each Scout project independently.

This configuration is considered when there is no possibility to choose explicitly a super class in the wizards: E.g. when creating a new Form by default there are also 'Cancel' and 'OK' buttons created. The default super class for OK buttons defined in this preference page will be used by the new Form wizard.

This mechanism also respects the new extensible Scout objects defined in org.eclipse.scout.rt.extension.client: If your project has this dependency, the Scout SDK prefers those objects over the standard ones (unless you have modified the defaults).

The settings are stored in the project preferences so that you can share them with your team using e.g. a team provider like SVN, CVS or Git.

Scout Project

With this drop-down list a project can be selected. This is where the configuration will be applied.

Type list and Filter

Depending on the type of selected project (client, server, shared) a list of types is provided. For each type you can select a super class with a drop-down list. If only one super class is available the value is selected and the drop-down list is disabled.

The "Type filter text" reduces the list of types.

See Also

Back to the top