Implement Layouting API

[Joonas Lehtinen]

See attachment.

[Jouni Koivuviita]

Client-side implementation missing, only IOrderedLayout does some alignment and margin stuff.

[Matti Tahvonen]

I suggest we forget the idea that layout must be sizeable. Implementing Sizeable on client side is not very easy task and having Sizeable methods in both container and it's layout is very odd for programmer (like panel and its layout).

• 100% width/height problems ( needs a lot of layout logic to be handled properly)
• deciding when use to scrollbars or to clip content
• basic layouts will need a lot more DOM elements on gwt-terminals client code

-> OrderedLayout? will be fat and buggy

Other enhancements ought to be pretty easily implemented.

Settings sizes in program layout can be set with:

• panel
• tabsheet
• splitpanel
• ExpandLayout? (needs horizontal orientation)

[Joonas Lehtinen]

Just to check, Matti: is the current impl strategy (implements Sizeable without any additional logic, overflow auto and 1div+1table dom-structure) for OrderedLayout? ok to you.

[Matti Tahvonen]

Yep, it's ok for me. I'm just working here :=) But I'm afraid that our layouts have too much to do now ( which makes their client side implementation too complicated with all the logic to layout themselves and to deal browsers differences in layouts and components inside them).

Tool (layouts in this case) that tackles every problem somehow rarely work good enough in real work. We have faced this problems previously with server-side Select component that did it all. Of course Swiss knife is an exception, but only for Mac Gyver.

But now we'll go on this route with a happy face and lets hope I'm wrong.

[Jani Laakso]

Two weeks left => We need code freeze ASAP => keep it simple => make compromises please!

Consequences: we will flush existing code (it is OK), re-design, re-implement after 5.0.0-beta is out.

[Jani Laakso]

Considering this done for beta, re-open if absolutely neccessary.