I just realized I failed to answer a couple of these questions... On Sun, Jan 3, 2010 at 5:56 AM, dflorey <[email protected]> wrote:
> - TabLayoutPanel has no default style and the given styles differ from > the TabPanel styles. Is it planned to add more substyles? > I added the bare minimum styles to get it working, but I anticipate that a better mechanism will be needed soon. We'd like to attack the general problem of using CssResource/ClientBundle to style widgets (and create broader themes) before letting the "old style" style names get to hairy. - Is an equivalent to DecoratedTabLayoutPanel planned? > I had something like the existing DecoratorPanel partially finished, but couldn't get it done in time for 2.0. The TabLayoutPanel itself defines two elements for each tab, which should be enough for most "sliding windows" style tricks, but without all the heavyweight mess of a full table for each tab. I've shown that you can at least duplicate Chrome's tabs (curved/angled with overlapping) using this structure. - Is there a simple way to let both widgets of a SplitLayoutPanel take > up 50% of the given space? > Not really. The SplitLayoutPanel requires PX units because it has to move the split-point in relation to mouse events, which are always in pixels. It *might* be possible to map mouse events to arbitrary units, but I didn't try to attack this problem in the first pass, mainly because I'm afraid of weird CSS aliasing artifacts.
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
