Brett,
You should be able to use the already-checked-in LayoutPanel to do anything
you could have done with AbsolutePanel before. And it should be the case
that you can get rid of all of your manual resize code (that's the
intention, anyway). Also, if you run into any problems embedding other
widge
Joel,
Will be happy to test new layouts and review API. Unfortunately, I
don't use Dock, Stack, or Split in my app. I do use Absolute. And
because of an interior scrolling area that fills the client, a
sprinkling of resize code (after beating my head against CSS for a few
days). I do use Form
The situation as I see it is this. The old layout "system" has two huge
problems:1. Some widgets (e.g., StackPanel) *cannot* be made to work as
expected in standards mode, because of changes to table rendering behavior.
2. It's not really a "system", in the sense that it can be highly
unpredictable
Cool. Then another question about the future of the new layout
system. Is the current thinking that eventually it *will* replace all
of the older panels? I mean, is there buy-in at Google that that is a
desired track for this project. Or will the new layout system remain
parallel to the origin
Brett,
I am going to be writing adding custom parsers for the new layout panels
sometime soon. And the new layout system will be "de facto" in the sense
that I'm updating all the samples to use it (and possibly adding another
sample). We obviously won't be removing the "old" widgets (e.g., StackPan