Consider splitting up your app into logical modules, not physical (GWT) modules. Your code will still be compiled into one large JavaScript file, which is good if it's not too big, but you can also speed up compilation by not loading unneeded modules while developing, i.e. if you comment out the loading code. Besides, you may find that this separation leads to a much cleaner application design.
loadModule(new UserManagement()); // loadModule(new ArchiveBrowser()); On 2 Sep., 00:26, jbdhl <[EMAIL PROTECTED]> wrote: > Thanks for all the replies! > > Can you agree that the following would be a good (very general) design > for a somewhat large application with a menu and sub-pages? > > 1) Each sub page is implemented in its own separate module > 2) A general module implements the general application (the menu and > right-pane containing the pages) > 3) The server-side code for each page is grouped somehow, according to > the functionality in the individual pages (however, several pages may > perform the same RPC calls, hmm) > > As you can see, it is still not clear to me. how such a larger > application should be structured. I really miss a GWT-template for > this (very common) kind of application with > * a left menu > * a "main pane" > * different pages such as "contact form", "product catalog", > "shopping basket", "help", etc, > and with a proper structuring/"partitioning" of both client- and > server side code. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
