Hi,

 I have some before and after code to show you. I sent it out earlier but since 
I didn't see it come back into my inbox I'll assume the HTML I put into it 
didn't pass the filters, so I've put the code into a paste[1] below.

I ran an example of the following MXML snippet. It is a series of nested 
Containers with different layouts.

Notice that the "after" is much smaller and there are fewer style ingredients. 
You can see that in the original MXML the only specific size specified was 
width="200" on the g2 Container. In the "before" HTML, that 200 appears in 
multiple places. In the "after" HTML, the 200 size appears only on the g2 
<div>, corresponding to the g2 MXML Container.  Now its up to HTML to maintain 
this structure and anything that happens to do (such as adding more children).

Finally, if a Container were to have the <js:ScrollingViewport> bead added to 
it, the only thing you would see in the HTML is overflow:hidden would change to 
overflow:auto for that particular <div>.

The SWF side hasn't been changed too much except that I have (at least I hope I 
have) improved the SWF-side layouts. Where the JS side may now only be as 
simple as style="display:flex; flex-flow:column", the SWF side will be an 
algorithm to mimic that. Over time I intend to improve that.

Apache Paste URL: https://paste.apache.org/HzAS

Reply via email to