Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of mark.kessler.ctr@usmc.mil
 designates 138.162.128.21 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: flash EventDispatcher and Event
Date: Thu, 25 Jul 2013 14:42:07 -0400
Message-ID: 
 <0E7CF6486AC44249B0B674C6760449B4068BB3A2@mcusquanez26v.mcdsus.mcds.usmc.mil>
In-Reply-To: <CE16ABD6.E103%aharui@adobe.com>
Thread-Topic: flash EventDispatcher and Event
Thread-Index: Ac6JXDppj/JJ+JZoStWZH9jvBO7etgAAiO8g
References: 
 <0E7CF6486AC44249B0B674C6760449B4042E3BE7@mcusquanez26v.mcdsus.mcds.usmc.mil>
 <CE16ABD6.E103%aharui@adobe.com>
From: "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>
To: <dev@flex.apache.org>

Well it did start with the issue FLEX-33608 [1].  They wanted to be able =
to remove all event listeners.  I had an old piece of code that created =
one time use listeners so I was able to toss together a work around for =
them.

But I went down the road of seeing what was feasible for being able to =
add simple functionality to the EventDispatcher anyways.   The W3C DOM =
event  Specification is understandable, but the problem lies with how =
Adobe implemented it.  They basically left method prototypes in the AS =
and execute all of it in the player. =20

Starling has this [2].  They've created their own event dispatcher to be =
able to gain control of this.

[1] https://issues.apache.org/jira/browse/FLEX-33608
[2] =
http://doc.starling-framework.org/core/starling/events/EventDispatcher.ht=
ml

-Mark

-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]=20
Sent: Thursday, July 25, 2013 1:27 PM
To: dev@flex.apache.org
Subject: Re: flash EventDispatcher and Event

Hi Mark,

I'm a bit lost on the context here.  The Flash Player is more or less
implementing the W3C DOM Event Specification.  Are you looking to =
enhance
it?  If so, why?  A whole group of people over at W3C decided this API =
set
was sufficient.  Or did I miss where they are also updating the
specification?

If this is related to the attempt to know who is listening for events on
an object, keep in mind that I've seen folks want to know that in order =
to
get all of those listeners to call removeEventListener, but I've never
really understood why, since those listeners do not cause a memory leak =
of
the object being listened to since the only reference is from the object
being listened to, to the object that is listening.

-Alex