Jump to: navigation, search

Difference between revisions of "Scout/NewAndNoteworthy/3.9"

(Migration Guidelines)
(New SDK Features)
Line 20: Line 20:
  
 
== New SDK Features ==
 
== New SDK Features ==
 +
 +
=== Default Super Classes are Customizable ===
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=395006 Bug 395006] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=397268 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 ===
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=394751 Bug 394751]
 +
 +
 +
=== More Flexible Project Structure ===
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=394125 Bug 394125]
 +
 +
 +
=== Improvements for the NLS Field ===
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=380507 Bug 380507]
  
 
== Bugfixes ==
 
== Bugfixes ==

Revision as of 06:26, 21 January 2013

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

General

Scout Sources moved to GIT

Bug 384960

For Kepler, Scout has moved to GIT: http://git.eclipse.org/c/scout/.

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

New SDK Features

Default Super Classes are Customizable

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

Bug 394751


More Flexible Project Structure

Bug 394125


Improvements for the NLS Field

Bug 380507

Bugfixes

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