|Re: I18N with single-sourcing [message #115502 is a reply to message #115489]
||Fri, 12 December 2008 14:25
Originally posted by: rherrmann.innoopract.com|
please see my comments blow.
Neil Bartlett wrote:
> What is the recommended approach to i18n in an RCP+RAP single-sourcing
> I have read the Help docs regarding i18n under RAP. That looks fine but
> the RWT.NLS class will not be available under RCP. I could use fragments
> to write separate implementations of the Messages class, but then I
> would have at least two fragments for every UI bundle in my application.
> Perhaps I could wrap the call to RWT.NLS.getISO8859_1Encoded() in an
> abstraction, then just provide two fragments for the whole application
> to implement that abstraction. Any thoughts on this?
The latter approach is recommended. You could create a
"compatibility plug-in" that would host abstractions for e.g. NLS
and other functionality that differs in RCP and RAP. As you
suggested, two fragments would contribute the respective
Some more information on this can be found in the webinar.
> By the way I tried to watch the recording of Frank's single-sourcing
> webinar on Eclipse Live but it doesn't seem to be available now.
The so called "buzz" page (http://www.eclipse.org/rap/buzz.php)
lists the recordings:
I was able to download and watch both of them. On EclipseLive I
couldn't find the webinar at all. Could you give me a hint?
Powered by FUDForum
. Page generated in 2.04311 seconds