Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RAP/1.0.1 Service Release News"
(New page: | RAP wiki home | [http://eclipse.org/rap RAP project home] | ===RAP 1.0.1 Service Release - New and Noteworthy=== As with every service release the main aspect is to provide bug ...) |
|||
| Line 11: | Line 11: | ||
|width="80%"| | |width="80%"| | ||
| − | See the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&resolution=DUPLICATE&resolution=WORKSFORME&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-15&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bug List] which contains all bugs fixed for this service release besides fixed items not tracked in | + | See the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&resolution=DUPLICATE&resolution=WORKSFORME&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-15&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 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 <code>SWT.VIRTUAL</code> flag. | ||
| + | Additionally selection bugs, empty labels and <code>pack()</code> of <code>TreeColumn</code>s are fixed. | ||
| + | |||
| + | <code>IProgressService#busyCursorWhile</code> is now blocking. | ||
| + | |||
| + | <code>StringFieldEditor</code> of JFace now throws <code>PropertyChangeEvents</code> in case of modifications. | ||
|-valign="top" align="left" | |-valign="top" align="left" | ||
| Line 23: | Line 30: | ||
|width="80%"| | |width="80%"| | ||
| − | The growing need for multi-language applications | + | 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. The full NLS support has influenced the <code>IDialogConstants</code> interface which now is a class. |
[[Image:RAPI18N.PNG]] | [[Image:RAPI18N.PNG]] | ||
| Line 31: | Line 38: | ||
|width="80%"| | |width="80%"| | ||
| − | 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 | + | 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. |
|-valign="top" align="left" | |-valign="top" align="left" | ||
| Line 37: | Line 44: | ||
|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 emtpy bodies to let your application compile. The RAP team is not proud if this solution or | + | 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 emtpy 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 [[RAP/Patch_Fragments Patch fragments]] how to use this technique and use with care. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
|} | |} | ||
[[Category:RAP]] | [[Category:RAP]] | ||
Revision as of 11:50, 7 December 2007
| RAP wiki home | RAP project home |
RAP 1.0.1 Service Release - New and Noteworthy
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 download.
RAP Common
| Fixed bugs |
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
|
| 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. The full NLS support has influenced the
|
| 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 emtpy 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 RAP/Patch_Fragments Patch fragments how to use this technique and use with care. |
