Le 24 mars 2015 � 15:56, Thierry Goubier <thierry.goubier@gmail.com> a �crit :

2015-03-24 15:39 GMT+01:00 Denis Kudriashov <dionisiydk@gmail.com>:

2015-03-24 17:36 GMT+03:00 Thierry Goubier <thierry.goubier@gmail.com>:
IMHO, Rubrics, just from it's layout approach, is already a step backward.

What you mean by this? What's wrong with Rubric layouting?

Padding -> resolved in Morphic by Morph composition: no need to add that to the Layout engine of each widget

Aligning -> resolved in Morphic by Morph composition: no need to add that to the Layout engine of each widget

I don�t get it sorry.

maybe one example would help

ZOrdering -> nothing says that submorphs in Morphic can't overlay each other.

Bloc uses z-ordering exactly as Morphic (the code for adding/removing a submorph are nearly the same)

Cheers

Alain

One of the issue with Morphic as it stands today is that the API is fairly complex if you want to carefully control placement and morph behavior under container resizing / move. Oh, and it's very buggy too. Rubricks shows an API which is even more complex, which isn't surprising if the inspiration is CSS layout.

Thierry