It seems that the super dev mode cannot benefit from the meta tag 
<https://code.google.com/p/google-web-toolkit/issues/detail?id=8175> defined 
within a dynamic host page. I originally tried switching to the cookie 
solution, but now I guess the compilation triggered by the bookmarklet 
simply ignores any locale-related info derived from the host page, such as 
the meta property, the query param and the cookie (set on host page domain).
But this way - supposed the gwt locale should reflect some data coming from 
a database - we have no way to make the superdevmode aware of the chosen 
locale.

Moreover, Thomas Broyer recently suggested 
<http://stackoverflow.com/a/16295300/2652766> to

> set the locale property to the full list of supported locales:
> <set-property name="locale" value="en,fr" />

in order to achieve dynamic internationalization. I thought simply 
extending the locale property with additional values was enough, but I've 
found no documentation talking about multiple values for this property.
But as soon as I define multiple values for the locale property, the 
SuperDevMode starts compiling too many permutations, eventually complaining 
*Multiple 
fragment 0 sourcemaps found. Too many permutations.*
I guess this happens because it has no way to reduce the permutations based 
on the chosen locale (in fact it doesn't log any *binding: locale=...*).

So my question is: what should I do in order to dynamically choose the 
locale used by SDM compiler?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to