I use a special "DevModule.gwt.xml" module during development that only compiles the permutations I am interested in. This way I can control the user agent, locale, and other GWT based switches without compromising the production builds. Below is a rough overview of this approach:
Create a new module file XXXDev.gwt.xml where XXX is the name of your applications top level module used for production builds. You will inherit your apps module from here. Set your various property overrides (e.g. "<set-property name='user.agent' value='safari'/>" and "<set-property name='locale' value='en'/>"). I personally use Ant to build my project and created a separate dev target that builds the dev module instead of the production module. Obviously, there are countless ways to orchestrate this but the basic idea is that you only compile the permutations you care about while doing development. You let an automated build/test system build the really big production builds and perform all of the automated tests. Hope that helps... On Tuesday, July 17, 2012 6:19:10 AM UTC-6, Rana wrote: > > Hi, > > Does anyone have a solution to the huge size of application, when we apply > to it internationalization using the static method? We are supposed to > support 66 languages. The application takes a long time during compilation > and the size of the application is huge, we cannot upload it to google app > engine. > > Many thanks > Rana > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Kc9KY4AhWp4J. 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.
