Perhaps the compiler just recompile Message etc type classes and have them in a separated *.js file. The problem with that is of course what about references to helper methods and the like that live in the "main" module. A mapping file would need to record names of said methods. There might also probably need to be a mechanism to avoid inlining a method in main that might need to be called from a "messages" module. I know this has been discussed before when others want the ability to "add" plugins to an application without recompiling.
On Thu, Oct 22, 2009 at 9:53 AM, John Tamplin <[email protected]> wrote: > On Wed, Oct 21, 2009 at 3:48 PM, Miroslav Pokorny < > [email protected]> wrote: >> >> It sounds like an alternative might be to have the compiler to spit >> out properties files full of key value pairs with one per locale. >> Naturally the compile would output shortened keys etc and record a >> mapping file. A tool would be made available to update just these text >> resources and the initial bootsrap code so it now picks up the newly >> updated files. The exiting use of cache files as much as possible >> would remain, but there would be less permuTation generated files. >> > > The problem is more than that. As mentioned above, the actual compiled > code is frequently different depending on the messages, such as when the > parameters are re-ordered in different locales or have different formatting > patterns. Basically allowing them to be switched outside of a full compile > means the format strings have to be parsed at runtime, which IMHO is an > expensive price to pay. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > -- mP --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
