Related thought, so I don't forget: It isn't clear that CSSShape and CSSTextField which are only used in SWF implementations needed to become HTMLElementWrappers.
-Alex On 7/29/16, 3:19 PM, "Alex Harui" <aha...@adobe.com> wrote: >In order to get Application to wrap the root, I will have to do more >mucking in this area. I may add createElement because it lets us control >what gets created as the wrapped element is a more common way. Otherwise >if a subclass wants to create a different element, the superclass will >have unnecessarily created a different element. > >Of course, I could be wrong... >-Alex > >On 7/29/16, 10:23 AM, "Alex Harui" <aha...@adobe.com> wrote: > >> >> >>On 7/29/16, 3:41 AM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>>Okay. I just implemented WrappedShape, WrappedSimpleButton, >>>WrappedSprite >>>and WrappedTextField. I hope that helps you. >>> >>>I did not implement a createElement method because I did not see the >>>point. On the HTML side there’s code that’s specific to a lot of >>>different individual elements, but on the Flash side it’s really simple. >> >>Well, on the SWF side there is current CSSShape, UIBase, UIButtonBase, >>StyleableCSSTextField, maybe others. With this change, these four >>classes >>can theoretically be collapsed into one (UIBase) where createElement >>creates the Shape, Sprite, Button, TextField, whatever. Then the >>lifecycle would be much more similar to the JS-side (or so I think). >> >>-Alex >> >
