> > Having lazy behavior in this LazyPanel, why not put it in other widgets > like the Composite ;)
Many API methods depend on the widget being initialized. We would have to cache a lot of values prior to initialization, or we'd have to have a really aggressive initialization policy, which could make debugging very difficult. If you don't expect a part of your app to be used immediately, you should initialize it lazily. You should also look at code splitting to break down the size of your downloaded app: http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html Thanks, John LaBanca jlaba...@google.com On Tue, Sep 14, 2010 at 7:51 AM, Ed <post2edb...@gmail.com> wrote: > Having lazy behavior in this LazyPanel, why not put it in other > widgets like the Composite ;) > > On Sep 14, 11:32 am, Thomas Broyer <t.bro...@gmail.com> wrote: > > On Sep 14, 9:47 am, dflorey <daniel.flo...@gmail.com> wrote: > > > > > I remember there once has been a LazyPanel in the incubator especially > > > for use within TabPanels. > > > > The one that graduated into GWT proper? ;-) > http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/g... > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
