As with every service release the main aspect is to provide bug fixed which didn't get into the 1.0 release. Here are some of the more noteworthy things available in the service release which is now available for [http://www.eclipse.org/rap/downloads.php download].

+

+

As with every service release the main aspect is to provide bug fixes which didn't get into the 1.0 release. Here are some of the more noteworthy things available in the service release which is now available for [http://www.eclipse.org/rap/downloads.php download].

==RAP Common==

==RAP Common==

Line 46:

Line 45:

|width="80%"|

|width="80%"|

−

Many users complain about missing API which is not yet implemented in RAP. As the RAP team decided to not implement [http://en.wikipedia.org/wiki/NOP NOP]s we still see the need of the community in order to "single-source" applications. With patch fragments you're now able to "patch" existing RAP bundles to add classes/methods by either implementing them yourself or just having empty bodies to let your application compile. The RAP team is not proud if this solution or encourages you to do this. We just wanted have at least the possibility to do so. See [[http://wiki.eclipse.org/RAP/Patch_Fragments fragments]] how to use this technique and use with care.

+

Many users complain about missing API which is not yet implemented in RAP. As the RAP team decided to not implement [http://en.wikipedia.org/wiki/NOP NOP]s we still see the need of the community in order to "single-source" applications. With patch fragments you're now able to "patch" existing RAP bundles to add classes/methods by either implementing them yourself or just having empty bodies to let your application compile. The RAP team is not proud if this solution or encourages you to do this. We just wanted have at least the possibility to do so. See [http://wiki.eclipse.org/RAP/Patch_Fragments fragments] how to use this technique and use with care.

|}

|}

[[Category:RAP]]

[[Category:RAP]]

Revision as of 05:52, 10 December 2007

RAP 1.0.1 Service Release - Release Notes

As with every service release the main aspect is to provide bug fixes which didn't get into the 1.0 release. Here are some of the more noteworthy things available in the service release which is now available for download.

RAP Common

Bugs fixed

See the Bug List which contains all bugs fixed for this service release besides fixed items not tracked by Bugzilla.

The tree widget has experienced some major rework regarding it's behavior with the SWT.VIRTUAL flag.
Additionally selection bugs, empty labels and pack() of TreeColumns are fixed.

IProgressService#busyCursorWhile is now blocking.

StringFieldEditor of JFace now throws PropertyChangeEvents in case of modifications.

Performance improvements

We addressed some critical performance issues in order to have better response times for the user of RAP applications.

Internationalization (I18N)

The growing need for multi-language applications led us to provide I18N support in RAP. With this your application will be translated based on the locale of the user. You only need to activate it and provide the translations for your application. See RAP/I18N I18N for more details how to use it.

With this effort on we had to turn the org.eclipse.jface.dialogs.IDialogConstants interface into a class. This may break code that uses this type.

RWT/JFace Standalone

To have the same abilities like the original implementation of SWT and JFace you're now able to deploy RAP applications without the dependency to an OSGi implementation (e.g. Equinox). This means you can use RWT and JFace standalone without the whole bunch of bundles sitting on top like the Workbench which is useful for simple applications.

Patch Fragments

Many users complain about missing API which is not yet implemented in RAP. As the RAP team decided to not implement NOPs we still see the need of the community in order to "single-source" applications. With patch fragments you're now able to "patch" existing RAP bundles to add classes/methods by either implementing them yourself or just having empty bodies to let your application compile. The RAP team is not proud if this solution or encourages you to do this. We just wanted have at least the possibility to do so. See fragments how to use this technique and use with care.