There isn't really any effect either way. The additional module might take a tiny bit extra time to compile (like under 1 ms) due to the compiler needing to read an extra XML file. But all of the code from all modules is flattened out at compile time into a single JavaScript file. So there is no runtime impact to using multiple modules vs. one module, and there really isn't a compile time impact that you can notice as a developer.
Generally people try to organize code into modules where there is reusability. Then its easier to reuse code from one project in another by just inheriting from the necessary modules. Its GWT's way of managing libraries. On Mon, Dec 29, 2008 at 14:32, rjcarr <[email protected]> wrote: > > Since I don't completely understand the GWT compiling / transcoding I > thought I'd ask a question about module organization and performance. > > I have a large GWT application that can logically be separated into > several modules. I would prefer that they are separated but I'm > curious the effects on performance, both compile time and run time. > > Is there any guidance that would help answer this question? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
