Is there a good reason why Flash, as of now, has 3 event broadcaster
solutions that appear to function in pretty much the same manner?
//BroadcasterMX (which i use commonly)
import mx.transitions.BroadcasterMX;
class MyClass{
public var addListener:Function;
public var removeListener:Function;
public var broadcastMessage:Function;
function MyClass(){
BroadcasterMX.initialize(this);
}
public function doSomething(){
broadcastMessage("onSomething");
}
}
//AsBroadcaster (which appears to be the same as the above)
class MyClass{
public var addListener:Function;
public var removeListener:Function;
public var broadcastMessage:Function;
function MyClass(){
AsBroadcaster.initialize(this);
}
public function doSomething(){
broadcastMessage("onSomething");
}
}
//EventDispatcher, which just looks awkward to me
import mx.events.EventDispatcher;
class MyClass{
public var addEventListener:Function;
public var removeEventListener:Function;
public var dispatchEvent:Function;
function MyClass(){
EventDispatcher.initialize(this);
}
public function doSomething(){
dispatchEvent({target:this,type:"onSomething"});
}
}
Especially i'm curious about the first two. I assume BroadcasterMX is to
be deprecated in favor of AsBroadcaster?
Why not one comprehensive event dispatcher solution to spare us the
confusion?
- Andreas R
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
