On Mon, Feb 8, 2010 at 6:04 AM, Luiz Mineo <[email protected]> wrote:
> I'm dedicating some of my time to develop a small framework, to help > me create and maintain big GWT apps. I'm already doing some really > useful things with generators, but one of my objectives is offer the > option to create a lot of modules, without the need to maintain a lot > of *.gwt.xml files, and let the developer choose what modules will go > to the final build, and what won't. For now, I'm trying to achieve > this with an standalone app that is executed before the compiler or > devmode, but I'm looking for a better solution. > > Is there any way to create or alter a module (like adding new source > paths) during compile time, using something like generators? Also, is > it possible to retrieve informations about the current module (name, > path...) in a generator? From what I could get from the GWT source, > it's not possible, but any idea would be appreciated =] > It is not possible currently to modify or create modules, and there is no API for accessing module-level info from a generator. As a philosophical point, we want to keep the generator API constrained so that we can make improvements to it -- for example, we are looking at adding generator dependency checking so generators can avoid being run if nothing they depend on has changed. What exactly would be accomplished by having a generator create a new module? The programmer will still have to specify to include it, and that might as well be in a module file with inherits. The generator can then create whatever types it needs based on generate-with rules in that module. -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
