This is a technique that I'm finding useful for using GWT to implement new features in an existing web application. The application already has a configuration-driven menu system that effectively resolves to a separate HTML file for each page. If I want to use GWT to implement new pages, I need to be able to configure what code to run when the page is loaded.
This could be accomplished using separate modules, but keeping all of the code in a single module reduces build time (separate modules require separate GWT compilation steps, as far as I can tell). With everything in a separate module, it's then just a matter of applying use of GWT.runAsync() so that only the code for the requested page is downloaded rather than the entire module. I had been doing all of this in a hand-coded dispatching entry point, but having an annotation- driven code generator instead makes a lot of sense as it removes the burden of maintaining that hand-coded entry point. -Brian On Jun 15, 12:37 pm, Stefan Bachert <[email protected]> wrote: > Hi, > > could you please tell what the benefit of multiple host pages should > be? > To me it still looks like a misconception because of still sticking > with concepts of pre-AJAX era. > > Stefan Bacherthttp://gwtworld.de > > On Jun 13, 1:33 am, Mark <[email protected]> wrote: > > > > > Hi, > > > There is now a project on Google Code (http://code.google.com/p/gwt- > > multipage/) for managing multiple host pages. And, tutorials here > > ->http://claudiushauptmann.com/andhere > > ->http://uptick.com.au/content/managing-multiple-host-pages. > > > Cheers > > Mark -- 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.
