> It doesn't explain the GWT-specific rules, but conceptually they're > not that different from the cc_library rules, or a Makefile for that > matter.
Just curious, but would stealing Lex Spoon's scala-gwt approach (writing .jribble ASTs to disk, like .class files), allow the Google build system to do more incremental analysis and so less recompilation? E.g.: 1. IDE or CLI compiles .java -> .jribble (resolved AST) 2. PrecompileModule bundles .jribble -> .gwtars 3. Compiler uses .jribble+.gwtars to generate .js output I guess the unit cache/gwtars were supposed to already solve this (avoiding reparsing of the AST), by caching ASTs. But then why do we still have the slow startup? E.g. why is not everything like primed superdevmode refreshes (which I, sigh, have still not played with yet)? - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
