On 6/15/15, 11:16 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
>>!!!!! Still having things at the root package level is going to cause >>problems, I think we need a solution to this, the CustomEvent and Event >>ambiguous warnings shows its probably going to mess things up. > >Can you give me an example? If you are using JS.SWC, what other swc is >going to define CustomEvent and Event? Again, the set of SWCs has to be >different for different targets. > >Well it happens if you want to use FlexJS and include DOM calls. Even if >you don't want to use SWF, CustomEvent is a DOM event class and at the >package level, so in IJ, it can't resolve CustomEvent in the class code >without it being qualified org.apache.flex.events.CustomEvent. OK, I get it now. We can certainly rename org.apache.flex.events.CustomEvent. For org.apache.flex.events.Event, I suppose we could rename it too. I have a feeling there would be some issue with doing that, but it doesn’t come to mind right now. Another option is revisit using goog.events.Event now that we’ve set the minimum on IE9 (instead of IE8). Maybe we can write a simple DOM non-bubbling Event implementation for objects that don’t wrap DOM objects. Would having or.apache.flex.events.Event extend Event or somehow map to Event fix the problem? -Alex
