I need to write a multi-locale app that allows the user to change
their locale at runtime. I would like to design the app so that I get
the maximum benefits of GWT's deferred binding functionality with
respect to locale.
I must allow the user to log in to the app in one locale (say de-DE),
and then later allow them to switch their locale setting to something
else (say es-ES) without logging out. Ideally I would initially only
load code and localization resources for the de-DE locale, and for
most users that would be sufficient. Other users may wish to
spontaneously change their locale, and at that point I would like to
only load the code and localization resources for the new locale (es-
ES or whatever).
My problem is that the nocache.js script does its locale-specific code-
swapping magic at boot time, and I would like to put that off until a
bit later in the app.
Can anyone recommend a strategy for achieving this design?
Thanks in advance!
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment