On 25 juin, 17:11, "Jason.Sadler" <[email protected]> wrote:
> Hello all,
> I have a fair bit of experience with GWT but am by no means an expert
> - I have a question about I18N.
> I am trying to introduce GWT UIs into a very large existing web
> application where there is a requirement that language packs be
> installable by the administrator of the web app.
> Using static I18N like Messages and Constants is (at least on the
> surface) not tenable because it requires a recompile every time a
> locale is added or edited, and I'm not willing to make the GWT SDK (or
> Java, for that matter) a server-side requirement. I suppose I could
> make some modifications to the bootstrap process to support hot-
> swapping of localized compiled JS in and out of the server. This
> would obviously require getting rid of the strong hashing naming stuff
> that gets applied to the GWT JS files, and I think this would require
> a significant amount of work.
> Going with the dynamic Dictionary method is also not ideal since the
> app is very large and so a lot of strings might have to be downloaded
> each time the page is loaded.
How is it different than GWT-I18N?
If I were you, I'd use Dictionary and have the JS dict loaded in an
external JS that's cacheable (if you can include some sort of "version
number" in the URL, then use "inifinite caching" just like with your
*.cache.html generates files).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
