Yes I understand how localization works and yes I understand the benefits of the way GWT handles localization and yes I am yet another whiner complaining about the speed of the compiles when localization is turned on and yes I know about speeding up compiles using - localWorkers etc, etc.
Anyway, I have an app and I'm using a Dictionary for localized strings and everything works great and whatever performance benefits I lose from not using compile time checking I can live with. The number of strings included in the dictionary is quite small. I would like to use the same technique for accessing DateTimeConstants and NumberConstants. Looking at LocaleInfo, there does not seem to be an easy way to access these constants using a dictionary technique. We use continuous integration for the builds which get deployed to a QA environment on a frequent basis. This build will get deployed to a production environment without recompilation. I recently added two locales and my build time jumped from 6 to 14 minutes. As we anticipate adding more locales the build time will increase even more. We want to make all locales available in the QA environments and don't want to push out a special build after testing in English. Is there a way of accessing the constants using a dictionary technique? If not, is there a way I can customize the build so that I can insert my own version of LocaleInfoImpl to load the constants from a dictionary? As an aside, if localized strings can be accessed from a dictionary, why not provide access to the constants in same way? I would appreciate any input. Thanks. -- 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.
