I agree with this. If I had to pick the single-most difficult thing when migrating from Flex to FlexJS, it would be layout.
The new layout beads are definitely improved over the older ones, but layout is not always necessarily as intuitive or performant as it might be. On the one hand, we don’t have constrained layout like we used to have in classic Flex. Being able to pin elements to specific locations relative to their containers and have it move/resize automatically by just specifying top,bottom,left and right values as well as percentages was REALLY convenient. To do that properly, we would need a more robust layout cycle than we currently have which brings along the overhead inherent with that. On the other hand, even the basic CSS based layout we have probably has too much reliance in DOM to be as performant as it otherwise might be. I imagine that we will ultimately have layout beads which go in both directions relative to what we currently have: Leaner beads which are more performant, and more robust beads which have more ease of layout. Harbs > On Jul 2, 2017, at 9:44 AM, Alex Harui <aha...@adobe.com.INVALID> wrote: > > Documentation is always a good thing, but as I've said several times, this > is bleeding-edge development. I'm just not sure we are ready to start > paving roads and putting up street signs. In Flex 0.8.0, we overhauled > the Layout subsystem and there are still things I don't like about it. > I'll bet there is one more overhaul coming up. I'm also pretty sure that > layout gets called too often but I won't know how to optimize until Harbs > or others get to the "last mile" and really start focusing on performance.
