Skip to main content
Jump to: navigation, search

Difference between revisions of "Scout/NewAndNoteworthy/3.9"

(Form Field Filter for FormData Import)
(New Runtime Features)
Line 27: Line 27:
[ Bug 396252]
[ Bug 396252]
=== SWT: Visual Marker in editable cell ===
[ Bug 395673]
A marker icon is now displayed in an editable cell in an SWT table (similar to the swing table).
The icon can be changed by setting the extension org.eclipse.scout.rt.ui.swt.scouticons for the cell_editable icon.
== New SDK Features ==
== New SDK Features ==

Revision as of 10:44, 3 March 2013

This page shows what you need to know about the new Eclipse Scout 3.9 release shipped with Eclipse Kepler.


Scout Sources moved to GIT

Bug 384960

For Kepler, Scout has moved to GIT:

For more information see Getting_the_Scout_Sources.

Scout EPP Changes

Bug 390431

Egit features added to EPP

CVS features removed from EPP. If CVS is needed, it has to be installed manually.

New Runtime Features

Form Field Filter for FormData Import

Bug 392409

Besides a IPropertyFilter the FormData import (method importFormData() in AbstractForm) now also allows to specify a IFormFieldFilter. With this overload it is now not only possible to influence which properties that are imported, but also which form fields that should be filled. A default implementation is available that allows to exclude some fields from the import (org.eclipse.scout.rt.client.ui.form.fields.ExcludeFormFieldFilter).

Multiple Swing Scout features in a single Eclipse application

Bug 396252

SWT: Visual Marker in editable cell

Bug 395673 A marker icon is now displayed in an editable cell in an SWT table (similar to the swing table).

The icon can be changed by setting the extension org.eclipse.scout.rt.ui.swt.scouticons for the cell_editable icon.

New SDK Features

Default Super Classes are Customizable

Default Super Classes Preference Page

Bug 395006 and Bug 397268

In Scout 3.8 when creating a new object using a wizard you already have the possibility to choose from a list of possible super classes. But the super class selected by default is always the same. So if you e.g. have defined a project specific template for forms called 'AbstractMyProjectForm' you always have to remember to change the selected super class when creating forms.

With Scout 3.9 you now have the possibility to configure the super classes that should be used by default for each Scout project independently: Go to Window -> Preferences -> Scout -> Default Super Classes. There you can specify the default super class to use for each object type and Scout project.

This configuration is also considered if you don't explicitly have the possibility to choose a super class in the wizards: E.g. when creating a new Form by default there are also 'Cancel' and 'OK' buttons created. If you now modify the default super class for OK buttons, this is automatically used by the new Form wizard as well.

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.

Variable Local RAP Target Location

Specify the RAP Target Location

Bug 394751

Modify the value of the scout_rap_target variable

If you are using a local RAP target (instead of a P2 update site) you may want to share your target definition with other developers using a team provider like SVN, CVS or Git. But there may be differences in the local path pointing to the RAP target (because you have a different setup or operating system). Or you may not yet have a local RAP target at all. This makes it hard to use a target definition in a team.

In Scout 3.9 you now have a new Eclipse environment variable called 'scout_rap_target'. So instead of using the local path directly in the target definition you can use the ${scout_rap_target} variable as a palceholder and each developer can then point this variable to the path where to find the plugins locally. The value of the 'scout_rap_target' variable is stored in the workspace and can therefore be different for each instance.

The Scout SDK also detects if you are using (or importing) a target definition containing this variable. And if you have not yet defined a location for the variable will ask you to define one or create a new RAP target location.

More Flexible Project Structure

Configure the default packages

Bug 394125


In Scout 3.9 the SDK does no longer rely on a specific package structure.

This affects the Scout Explorer which now searches for objects in a whole plugin instead of specific packages. As a consequence the folder 'Process Services' and 'Outline Services' have been merged to a general 'Services' node containing all services except lookup and the common ones. This gives you more flexibility in usage and design of your services.

Furthermore you have the possibility to specify the target package when creating new Scout objects using the Scout SDK Wizards. The packages where new objects are created by default can be configured using the preference page: Window -> Preferences -> Scout -> Default Packages.

These settings are stored in the Scout project preferences and can therefore be shared using a team provider like SVN, CVS or Git.



Improvements for the NLS Field

Bug 380507

We have changed the sorting and presentation of the NLS proposal field so that the list behaves more intuitive and that it is more clear why a match is included in the list. This includes separation of the matches depending on type and sorting according to relevance.

NLS Field Changes


The following list shows all bugs which have been fixed for this release. The list also contains all new enhancements.

Migration Guidelines

Some features and bugfixes sometimes require a change of the api. If this has been the case for the new release then you'll find behind the link below a guideline how to migrate your scout application to the newest release.

Migration Guidelines for 3.9

Back to the top