I have not looked into this at all.  FWIW, ED is spec'd to support bubbling and 
it should be possible for a RoyaleUnit test to rely on bubbling, so maybe the 
issue is that the support for bubbling has undesirable dependencies?

On 5/14/20, 10:45 AM, "Carlos Rovira" <[email protected]> wrote:

    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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C9a34b8b369e346d319c608d7f82e97ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250751309179283&amp;sdata=AOLMoT%2FnhQm%2B1IF8rVM0%2FrD6AvEWv4Bev7svEE9nkF4%3D&amp;reserved=0>
    >
    
    
    -- 
    Carlos Rovira
    
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C9a34b8b369e346d319c608d7f82e97ed%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637250751309179283&amp;sdata=64OYco9N8cd%2F7u5BvWZt2RzlDiZVMvAa2F0c14%2FuBHY%3D&amp;reserved=0
    

Reply via email to