You can have more than one entry point in an application and it will make no appreciable difference to the compile time, caching, compression, reuse or deployment time
Same goes for splitting your application into different modules. What *will* make a difference is if you produce different versions of the application for different situations Ian 2008/8/27 jhulford <[EMAIL PROTECTED]> > > On Aug 27, 7:49 am, walden <[EMAIL PROTECTED]> wrote: > > Sam, > > > > It's possible (and documented in the archives of this list somewhere) > > to use a single EntryPoint to instrument multiple HTML pages with > > GWT. The mechanism is to have the EntryPoint code discover which HTML > > document it is running in, and then switch on that. But that's > > probably premature optimization in your case, and I would avoid it for > > now. Simpler to create an EntryPoint/Module for each page you > > currently have, and use Module inheritance to reuse code. > > You're not going to get the full benefit of caching / compression / re- > use by doing that though. Each different entry point / module will > result in a separate set of javascript files. There's definitely a > trade-off in that 1 separate module per page is easier to maintain, > but using 1 monolithic module will more than likely get you a better > user experience. You'll also increase your deployment compile times > quite a bit doing many different entry points. > > > > -- Ian http://examples.roughian.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
