mmm... a plain RTFM would have been enough ;) thanks for waking me up Michael
On Feb 26, 12:07 pm, obesga <[email protected]> wrote: > See 'ConstantsWithLookUp', may them help you. > > But the class you're looking for is 'Dictionary', which lets you > implement a dynamic localization. > > http://code.google.com/intl/en/webtoolkit/doc/latest/DevGuideI18n.htm... > > The hard part - that you must resolve - is how to mix dinamic and > static I18N. > > Hope it helps > > And Dictionar > > On 25 feb, 20:43, mmoossen <[email protected]> wrote: > > > Dear all! > > > i was wondering what is the best way to add support for a new locale > > without compiling the whole module again. > > > my use case, to distribute a CMS plugin written in GWT and we want > > that users can easily localize it. > > > in java. you just put an additional properties file to the right > > package in the classpath (not even the same dir). > > as i understand, for client-side localization with GWT this should not > > be possible. > > > so, i am trying to figure out what the best way to achieve this might > > be? i was thinking in having server side resource bundles and one (or > > several) RPC services for serving the localized strings to the client, > > most likely having a RPC method as: > > Map<String,String> getKeys(Locale locale) > > the main problem with this would be to ensure keys are loaded before > > starting the app. > > > it wont be so elegant as native GWT localization, but it could work > > well enough... > > > another idea i just got: > > to generate the localized keys as JSON into the JSP host page. mmm.. > > sounds better than the previous idea :D > > > what is your advise? > > > thanks > > Michael -- 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.
