On Fri, Jan 9, 2009 at 4:36 PM, jed <[email protected]> wrote: > What am I doing wrong ? Any ideas ?
You're not doing anything wrong. For performance reasons, the GWT compiler generates several monolithic scripts (one for each browser, and there are some other axes of specialization). Notice that you only give the compiler one module name and that module includes a bunch of other modules, and those modules may do the same, recursively. You end up with a "tree" of modules. (Tree is in scare quotes because you might get cycles in the imputed graph, so there's no guarantee that it's actually a tree in the strict sense.) You only give the root of the tree to the compiler and the compiler uses that root to define the scope of the application it's compiling. You'll get one set of output files that each include code for the entire application, specialized along some set of axes. I think you're worried about how to reuse the code in the administrative panel that you've worked hard to separate. The answer is to write another GWT app that also makes reference to that module in its root module. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
