Eclipse Community Forums: Remote Application Platform (RAP) » Internationalization: stacked views are not all showing localized names

Home » Eclipse Projects » Remote Application Platform (RAP) » Internationalization: stacked views are not all showing localized names(Localization works properly initially, then when log out, and log back in with different locale, only initial view tab is localized.)

Show: Today's Messages :: Show Polls :: Message Navigator

Internationalization: stacked views are not all showing localized names [message #846789]

Mon, 16 April 2012 18:56

George R Malary

Messages: 36
Registered: March 2012
Location: New Jersey

Member

Localization is working pretty great. Very nice implementation, and seems pretty easy to mantain. I am having some weird behavior though. Here is the scenario:

When login, there are 2 views, stacked, so can see both tabs, and the initial tab is shown.

1) Set locale to english, and login. Everything looks fine.
2) Logout and set locale to spanish. Then login.
3) The first tab that is showing has the correct localized title. The second tab still shows the english title.
4) Click on the second tab, and the second view shows, and the tab is now displaying the correct localized title.

Could this have anything to do with server side caching? Any suggestions on how to fix this, or what the problem can be?

Thanks and regards,

George

Report message to a moderator

Re: Internationalization: stacked views are not all showing localized names [message #847344 is a reply to message #846789]

Tue, 17 April 2012 08:01

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

The problem is the same with Eclipse RCP and is caused by the fact that
on the second start the UI is restored from a saved file (workbench.xml)
and there the "wrong" string is saved. There's no Java-Code executed
until you select the Tab.

Eclipse 4.x can solve this (can because the current compat layer doesn't
support it) because there translations are a so called decoration
process but even if it would solve it RAP has not yet adopted the
Eclipse 4 Platform.

Tom

Am 16.04.12 20:56, schrieb George R Malary:
> Localization is working pretty great. Very nice implementation, and
> seems pretty easy to mantain. I am having some weird behavior though.
> Here is the scenario:
>
> When login, there are 2 views, stacked, so can see both tabs, and the
> initial tab is shown.
>
> 1) Set locale to english, and login. Everything looks fine.
> 2) Logout and set locale to spanish. Then login.
> 3) The first tab that is showing has the correct localized title. The
> second tab still shows the english title.
> 4) Click on the second tab, and the second view shows, and the tab is
> now displaying the correct localized title.
>
> Could this have anything to do with server side caching? Any suggestions
> on how to fix this, or what the problem can be?
>
> Thanks and regards,
>
> George
>

Report message to a moderator

Re: Internationalization: stacked views are not all showing localized names [message #847636 is a reply to message #847344]

Tue, 17 April 2012 14:00

George R Malary

Messages: 36
Registered: March 2012
Location: New Jersey

Member

Thanks for the reply Tom. I imagined something like that was happening, and it seems no the solution is not on the near horizon for RAP.

Any suggestions for workarounds?

I was thinking of maybe activating each view on login, and then go to default view, so that the title is refreshed with localized values. If possible turn off redraw, so user does not see what is happening? Is something like this feasible and correct? Just looking for some thoughts before I spend too much time trying to work around this issue.

Regards,

George

Report message to a moderator

Re: Internationalization: stacked views are not all showing localized names [message #848711 is a reply to message #847636]

Wed, 18 April 2012 14:00

George R Malary

Messages: 36
Registered: March 2012
Location: New Jersey

Member

My co-worker Ronald suggested trying the following:

Add the following in ApplicationWorkbenchAdvisor : configurer.setSaveAndRestore(false);

This works, and probably for the reason you suggested, that the workbench.xml is no longer used. My question is what are the repercussions of turning this off? What other information is stored? I would not want to keep this as a permanent solution, and would probably want the benefits of using the workbench.xml to store some information, like layout or preferred sizes.

Report message to a moderator

Previous Topic:	A tutorial about Single Sourcing with RAP
Next Topic:	RAP app with BIRT--is there a way to use interactivity

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 14:21:14 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter