In additon to what Mahavir have said - you can (but it's really up to you) use lazy loading to load your tab-classes on demand. Use LazyPanel or other lazy-loading methods if you need.
On 24 Feb., 08:11, Mahavir Jain <[email protected]> wrote: > Its up to you how to implement.. But I would like to put the tab panel in > main class.. Then I will create the custom widget which is container for all > widgets in particular tab. That widget will be in my different class.. > Similarly for all the tabs.. In main class I will add my custom widget into > tabpanel > > Mahavir.. > > On Tue, Feb 24, 2009 at 4:11 AM, [email protected] > <[email protected]>wrote: > > > > > Hi > > I have what is right now a single page GWT app... works good. > > But now I realize I have a few other pages of stuff and would like to > > put these on tabs. > > My question is about the best way to do this. > > Should I have one huge class which contains the TabPanel, all the tabs > > and their contents..... Or could I have a separate class for each tab, > > and draw them all together in the entry-point class? > > For example, I'd want a tab called "Home/About" which contains some > > basic info... then a tab called App 1, which contains several panels, > > text areas, etc., then another tab called App 2, with a bunch of stuff > > on there. > > I'm thinking I should be able to build each of these as their own > > class, and load/create them from within the "main" class if/when their > > respective tabs are clicked on. > > Does that makes sense? > > Thanks! > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
