Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Internationalization of "Core Plugins"
Internationalization of "Core Plugins" [message #119793] Tue, 27 January 2009 17:22 Go to next message
Markus  rüger is currently offline Markus rügerFriend
Messages: 369
Registered: July 2009
Senior Member
Hi,

I have a question. We are developing a new Product with RAP. Usually when
developing eclipse RCP we split our plugins in "core" and "ui" plugins. The
"core" plugins usually have no references to any "ui" plugins. Now using
this concept for RAP seems to fail with internationalization as the class
"RWT" that is responsible for translation resides in a "ui" plugin.
Does anyone face the same problem and/or has a solution for this?

Regards,
Markus
Re: Internationalization of "Core Plugins" [message #119882 is a reply to message #119793] Tue, 27 January 2009 20:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: adv.zahn.googlemail.com

The problem is that - in RAP - the decision for the user's language can
be made for incoming requests. So I think you have to decide

- system output, e.g. when starting the application (locale is the
JVM's system locale)
- UI output, for that you can use the RWT.NLS class

The result is, that - for system output - you cannot use RWT.NLS if you
want to split in core and ui. Instead, you can use ResourceBundles or
the "good old" org.eclipse.osgi.util.NLS class?

Regards,
Ralf

Markus Krüger schrieb:
> Hi,
>
> I have a question. We are developing a new Product with RAP. Usually when
> developing eclipse RCP we split our plugins in "core" and "ui" plugins. The
> "core" plugins usually have no references to any "ui" plugins. Now using
> this concept for RAP seems to fail with internationalization as the class
> "RWT" that is responsible for translation resides in a "ui" plugin.
> Does anyone face the same problem and/or has a solution for this?
>
> Regards,
> Markus
>
>
Re: Internationalization of "Core Plugins" [message #120027 is a reply to message #119793] Thu, 29 January 2009 11:00 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
Markus,

in my opinion, core code should not deal with locale specific
information regarless of the implications that RAP brings into the
topic. Code that needs access to locale information should stay in
the UI thus the problem wouldn't arise in the first place.

If your code plug-in actually needs locale information, you would
need to pass it there from your UI code.

Cheers,
Rüdiger


Markus Krüger wrote:
> Hi,
>
> I have a question. We are developing a new Product with RAP. Usually when
> developing eclipse RCP we split our plugins in "core" and "ui" plugins. The
> "core" plugins usually have no references to any "ui" plugins. Now using
> this concept for RAP seems to fail with internationalization as the class
> "RWT" that is responsible for translation resides in a "ui" plugin.
> Does anyone face the same problem and/or has a solution for this?
>
> Regards,
> Markus
>
>
Re: Internationalization of "Core Plugins" [message #120159 is a reply to message #120027] Fri, 30 January 2009 12:57 Go to previous message
Markus  rüger is currently offline Markus rügerFriend
Messages: 369
Registered: July 2009
Senior Member
Ok, thank you for the information.

"R
Previous Topic:Plugin in for UI design.
Next Topic:Changing default Font / Theming
Goto Forum:
  


Current Time: Wed Dec 01 20:46:14 GMT 2021

Powered by FUDForum. Page generated in 0.02306 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top