Don't think in "pages." You have a UI which is defined by the components it contains. You just need to identify these components and how they interact with each other without really knowing each other / depending on each other. Use UML diagrams to get the big picture but focus on one or two components when you start implementing your app. Use design patterns like MVC and observer/observable. This is pretty basic UI design stuff that you can find in a lot of books. It's not GWT-specific. And if you do it like this it doesn't really matter whether you write small apps with 10 components or "monsters" like Google Docs.
Of course, there are some GWT-specific things like history support and whether your application state sets or "follows" the history token. But there's no general solution to that either. It's all up to you. On Sep 2, 1:26 pm, jbdhl <[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. > > I'm a newbie to GWT, admitted, and I basically I try to figure out how > to structure the code for the different pages in my application(s). > > > You definitely haven't if you think you need templates. > > Hehe, no of course not. I meant "templates" as in "example". »An > *example* application of that kind would be appreciated«, I meant. :-) > > > Start off with something simple, like replicating Gmail's functionality. > > That would be one application, one module and one entrypoint. > > OK, point taken. > > > Send me a spec for this mystery site of yours, and I'll send you a simple > > basic design. > > If you really want to use that much time to help me - even though you > don't know me - I would be *very* *extremely* thankful!!! > > My basic site is conceptually very similar to gmail. It consists of: > 1) a left menu and a main pane. > 2) a box in the left menu containing the users "rating" (which is > updated regularly) > 3) a menu entry for the "front page" (default page) > 4) a menu entry for a "settings page" > 5) a menu entry for message threads that the user is involved with > 6) a menu entry for a write-new-message form > 7) the page displaying the individual message threads > > On a different subdomain, "admin.example.com", I will make an > administration site for administrating the main site. The admin site > has same structure as the main site with a left menu and a main pane > and clearly I'm interested in making the two sites (main and admin) > share as much code as possible. > > My question is now: What would be a good design/structure for these > "monsters" with respect to both client- and server side code? > > Thanks again! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
