On Thu, Aug 6, 2009 at 1:41 PM, Joel Webber <[email protected]> wrote: > Please do have a look and see what might be done to make this easier. The > names are definitely the most negotiable part of the design, and I'm > definitely open to other ways of handling the "RootLayoutPanel" problem. The > biggest issue I have with it at present is that there's no way to get() a > RootLayoutPanel for an arbitrary element -- I think this is impossible in > the general case, because there's no way to know when an arbitrary element's > size has changed. The other design problem that I'm not terribly happy with > is that there's no way to enforce that a widget that "RequiresLayout" be > added to a panel that "ProvidesLayout". Again, I'm not sure that there's a > perfect solution to this problem, but I'm quite open to ideas. >
I think you could have an "ExternallySizedLayoutPanel" that acts like a RootLayoutPanel but it is up to the user to let it know when its size changed. You could then inject it into an existing page, but you would be responsible for sizing it appropriately. This is assuming I understand the fundamental limitation you are worried about. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
