On 2/25/17, 6:33 AM, "Peter Ent" <p...@adobe.com> wrote:
>Maybe we need a big refactor. Things like effects are pretty advanced and >maybe they should get coupled with more advanced/complex layouts that are >in a different package than HTML. Well, I don't know how to define "big", but we do need to get it right, and I think we have more good real-world use cases to consider. Effects should plug-in and be PAYG like anything else, so sure there might be Effects-knowledgable layouts, or Effects-capable components (where setting x,y,w,h first dispatches a cancelable "changing" event that the Effects system cancels. Or maybe Effects is a completely different API than regular Flex where you use EffectInstances as proxies to change the actual properties on the display objects. Or all of the above since there doesn't have to be only one way to do things. If you can live with visual cruft you can have a smaller, more primitive effects system. I just noticed on my phone that when it is running slowly, that the slide switch that turns on my mobile hotspot actually gets reset back to the off position and animated to on. > >The basic packages could be simpler layouts that do minimal settings. The >HTML package could be JS only and just wrap the HTML elements for use >with ActionScript. In the dual branch, the HTML package only contains the <a><h1> kinds of components. Basic contains the more Flex-like controls. My 2 cents, -Alex
