Of course there are many ways of skinning this particular cat. Here is one...
* Treat entry points as components on a web page. An EP might just be a menu or it could be the entire page. Prefer the latter if you're starting from scratch * I like to keep all the logic in one place - the one place in this instance is Java. I find it easier to maintain the app when all my layout logic is done in one language. Exception: styles. Define all styles in CSS file(s). Have a plan for defining style names and do that, and only that, in Java * Use a single index.html with a basic layout that is reused for the whole of the application. It may be that you want two or three major layouts - e.g you might want a catastrophic error message page. Keep these to a minimum for the user's sake * Figure out the major contexts of your application: user not signed in, edit preferences, create order, browse catalogue, ... I call these 'contexts', others call them 'places' * Put a working area in your main layout - this is where your contexts will be presented one at a time * Manage your contexts using the GWT History component * Use Composites to encapsulate, simplify and clarify complexity --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
