On 6/15/15, 11:42 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
>>>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? >> >> > >This is not a solution though. I only used Event and CustomEvent as an >example because that is what IJ initially complained about in the >DataBindingExample. > >But this would hold true for all package level DOM classes if you had the >same name with an import statement in your code. But realistically, how often will there be collisions? This has always been true for Date, Array, etc, right? What else is in there that folks will collide with, and only if they want to go low-level? -Alex
