Hi Josh, I was in the believe that the bubbling changes to ED was PAYG and was done to be composed. I think that would be the best, if done in a way where we can easily use with bubbling in the framework and without it in RoyaleUnit. If that's possible, I'd like that instead a ED duplicate class.
Thanks El jue., 14 may. 2020 a las 0:24, Josh Tynjala (<[email protected]>) escribió: > FYI — It appears that Royale 0.9.7 breaks the ability for > org.apache.royale.events.EventDispatcher to be used in Node.js. This means > that RoyaleUnit can no longer be used with Node.js, which was one of my > original goals for RoyaleUnit. Unfortunately, while I tested that one of my > Royale Node.js command line tools was working correctly with the RC, I > guess that I forgot to run its RoyaleUnit tests too, so I missed the > effects of this change until now. > > The change seems to be related to adding bubbling events to the > EventDispatcher class. EventDispatcher now depends on IChild, which has > some properties of type WrappedHTMLElement. WrappedHTMLElement depends on > HTMLElement, which obviously isn't available in Node.js. > > Not sure about the best approach yet, but one possible solution is to > create a new superclass of EventDispatcher. The superclass would handle > events without bubbling. The subclass would add bubbling support. As a > bonus, this would be more PAYG because it will allow projects to exclude > the bubbling code if they don't need it. I don't know if I'll get a chance > to implement this soon because I'm still knee-deep in compiler stuff, but > it's something that I'd eventually like to fix because my Royale Node.js > projects will be stuck on 0.9.6 without it. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > -- Carlos Rovira http://about.me/carlosrovira
