Layouts with constraint classes

[Tom Eugelink]

On 2012-11-30 09:13, Tom Schindl wrote:
> We are not obliged to use it but if wanted we can and if we don't have the setLayoutConstraint()-API on the node I can't. Having this layout-constraint API on Node gives us both what we want: a) you can have the convenience API on layout b) I can still use bulk operations c) There's not change needed in FXML infrastructure 

I believe 99% of the use cases will not involve operations that benefit from getChildren; most use case will be simple "add-node-to-layout-with-specific-constaints". This is what the API should be optimized for. Maybe we can find some source that helps us define the most common use cases.


> I understood Richards last comment in the way that having the layout-constraint on each node has the benefit that no changes to FXML are needed. I think what Richard and myself are after is to have an API that allows to have a Java-API which does not make the FXML case harder.

But the things that are needed to make FXML not harder (or make the FXML format readable) should not pollute the Java API. Glue IMHO should be put in a separate class or file.

Tom