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. I followed the same pattern with flexjs_wrapper (i.e. a var rather than a getter/setter), but that seems to me like it makes the IFlexJSElement pointless because the interface does not declare anything. Using getter/setters instead of variables makes more sense to me for that. Thanks, Harbs On Jul 29, 2016, at 9:26 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 7/28/16, 11:05 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> I’m also not understanding what positioner does. Why can’t you get a >> reference to the parent element from the FlexJS parent? > > Positioner and element are often the same in JS, but sometimes the element > is an <input /> of some type wrapped in a outer <div /> with a sibling > label and you want to position the positioner, not the child element. > >> >> >> On Jul 29, 2016, at 9:00 AM, Harbs <harbs.li...@gmail.com> wrote: >> >>> Cool. >>> >>> I’m not totally getting the use case of the IFlexJSElement, but there’s >>> definitely nothing wrong with adding a wrapper class that extends a >>> Flash type. > > I may have to implement these changes to get the event proxy to work. On > the JS side, the event.target is the wrapped DOM object and you often want > to know which HTMLElementWrapper wraps it. > > -Alex >
