2018-03-27 9:02 GMT+02:00 Harbs <[email protected]>: > > The thing we should try to avoid is mixing absolute positioning and css > positioning of elements. Mixing the two probably gives the worst > performance. > > I am trying to stick to the topic which is how to enable measuring and > deferred layout when needed, but avoid it when not. > > I think this is very important. We should have a layout base that doesn't implies computation. Then will be code for JS and code for SWF. SWF code will need lots of code since in Flash there's no native rendering engine the provides that functionality, so is up to our code. JS code will be mostly setup a css class on the object, or will apply, paddings and margins on child objects. So all is up to the browser rendering engine and no more calculations are done, so that's for sure the most optimal or performant scenario.
Then, if we need more and to be extensible, people that wants to go other path should be able to have extend and provide js calculations for more complex scenarios. But my guess is that very few people will want to use that kind of scenarios, or as browsers evolve, more needs will be cover in the rendering engine and we only need to support it via css. (Now is Flex due to browser support, then will need to use Grid as will be more adopted, and so on...) At least that's what I see. -- Carlos Rovira http://about.me/carlosrovira
