Layouts with constraint classes

[Tom Eugelink]

On 2012-11-30 10:10, Daniel Zwolenski wrote:
> Disagree that there are not a lot of use cases for getChildren (observable/binding would be a start) but the point is completely moot since I would guess there is a big fat zero chance of that kind of change happening - backwards compatibility won't even let us have interfaces "just in case", getting rid of getChildren would be out of the park. 

Correct, my approach does not get rid of getChildren; it is a very value collection, it just not the optimal API for developers IMHO. Richard also said he would like to deprecate the static methods. I agree, so that is my focus.

The builders could indeed make the API better, but they're basically a workaround. And it fails to address the multiple layouts scenario. So knowing we're going to have a long lived legacy there, let's not make it more heavy. (Although I'm a proponent of cleaning up deprecated stuff on major releases.)

Tom