True. I hope the out-of-process hosted mode ( http://code.google.com/p/google-web-toolkit/wiki/DesignOOPHM) will alleviate the need to recompile the app every time for "firebugging".
On Sun, Aug 31, 2008 at 10:00 AM, George Georgovassilis < [EMAIL PROTECTED]> wrote: > > There is a reason to split an application into several modules: > compile time. As an application grows in size the hosted mode reload > process will become slower and slower, and compile times for the gwt > compiler will take several minutes which can be particularily annoying > if you're battling with layout problems in a browser different than > the hosted mode implementation. > > On Aug 30, 8:10 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > Page1 and Page2 would just be widgets in their own class, all in the same > > application. > > > > Unless the application is large (very large) then there's no need to > split > > it up into individual modules. > > > > How ever you split it up, there would be one application produced by GWT > to > > upload, and one class for each page. Obviously common code for any page > > could (should) be in an abstract class the actual pages inherit from, but > > nothing more complicated than that. > > > > Imagine a HorizontalPanel. A label on one side, a blank SimplePanel on > the > > other. > > > > When you click the label, you put an instance of MyPage in the > SimplePanel > > > > Click label...See page > > > > Now put two labels in the LH side (in say a VerticalPanel because each HP > > cell can contain only one widget). > > > > Click label...See page > > Click other label...See other page > > > > That's it, that's your menu-based site. (At least that's the suggestion). > > > > No need for multiple modules or anything complicated > > > > That's what my examples site is based on, the only difference is that > when > > you click a label, you may find the whole system repeated (nested) so I > can > > have nested menus > > > > I don't know how complicated your variable menu system needs to be, but > it > > would be easy to add items at the end of the menu when you click one of > the > > labels (removing the old ones from the previous menu first) > > > > No monolithic code if you design it right. At least, the only monolithic > > code is the JS produced by GWT. > > > > Ian > > > > http://examples.roughian.com > > > > 2008/8/30 jbdhl <[EMAIL PROTECTED]> > > > > > > > > > > I'd split the page in two with a horizontal panel. > > > > > I like that way of doing it. But how should I structure the code for > > > the individual sub-pages? In separate modules? More specifically: How > > > would you structure the > > > 1) client side code and > > > 2) sever side code > > > to reflect that the application has been split up into several pages? > > > > > I would really like to avoid maintaining a large monolithic chunk of > > > code. > > > -- Renato Mangini http://www.linkedin.com/in/mangini --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
