> Start off with something simple, like replicating Gmail's functionality. That would be one application, one module and one entrypoint. I don't think I necessarily agree with this. It would completely depend on how you implement code reuse on your site. If there are widgets, like he mentioned which would go on multiple pages, wouldn't it make sense to put them in a different module?
So, basically what i'm saying is: if your site has a few pages with common widgets then maybe it may be better to have modules and if there is just 1 large application then a single module site may be best. -Pavel On Tue, Sep 2, 2008 at 5:00 AM, Ian Bambury <[EMAIL PROTECTED]> wrote: > I'm not sure you have got the hang of GWT if you think you need a different > module for each sub-page. > > You definitely haven't if you think you need templates. There will be one > HTML page with all but nothing in it, so where is the need for a template? > > If you want a template for 'a left menu and a main pane' put a vertical > panel and a simple panel in a horizontal panel. and save these three lines > of code somewhere. > > Unless your site has large chunks of disparate functionality (e.g. a > fully-functioned email client, a comprehensive word-processor, and an > on-line shop with thousands of products in many different categories) then > you don't need more than one module, and under those circumstances, you > would probably have separate applications. > > Forget separate modules: you either a) don't need them because an > application your size doesn't warrant it, or b) you are attempting something > really stupidly large for someone starting out with GWT (like replicating > the BBC web site). > > Start off with something simple, like replicating Gmail's functionality. > That would be one application, one module and one entrypoint. > > Send me a spec for this mystery site of yours, and I'll send you a simple > basic design. > > Ian > > > > 2008/9/1 jbdhl <[EMAIL PROTECTED]> > > >> 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 -~----------~----~----~----~------~----~------~--~---
