I remember there once has been a LazyPanel in the incubator especially
for use within TabPanels.
Can you by chance provide your SimpleComposite src?
Thanks,
Daniel
On Sep 12, 5:04 pm, Ed post2edb...@gmail.com wrote:
I've never used lazy-loading within my
composites and never felt the need
I just uploaded the latest version of SimpleComposite in the issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=2508
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.
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? ;-)
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
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
Thanks John,
I am familiar with the lazy loading and code splitting and use it a
lot as it's an important issue in my gwt app's.
That's one of the reasons that SimpleComposite came to existence.
Many API methods depend on the widget being initialized. We would have to
cache a lot of values
On Sep 12, 1:57 pm, Ed post2edb...@gmail.com wrote:
I long time ago I opened an issue about the Composite
widget:http://code.google.com/p/google-web-toolkit/issues/detail?id=2508
I think the Composite widget should be improved because:
1) Creating all widgets in the constructor is an
I've never used lazy-loading within my
composites and never felt the need for it;
Lucky bastard ;)
Of course you should always create your widgets as late/lazily as
possible, but still.. it's not always that clear in complex app's with
many nested widgets.
As such, by embedding this behavior
