I'm surprised that this thing works (i mean monkey patching). I think It's the worst case of code coupling. The use with event listeners is rare case when this approach is OK. I've started using FlexSpy with Events Listeners just now - it's great :) Thanks
Andrii Olefirenko --- In [email protected], "Doug McCune" <[EMAIL PROTECTED]> wrote: > > It's a "feature" of the flex compiler, which will take the newest version of > any of the classes that it finds and use that version in the final app. So > when you name classes exactly the same as the Flex framework classes (in > this case mx.core.FlexSprite) then the compiler will use your local version > instead of the version in the framework. On other languages similar > functionality is called monkey patching, so that name has kind of stuck for > this approach. > > Doug > > On 2/21/08, Jerome Clarke <[EMAIL PROTECTED]> wrote: > > > > is that a bug or something in the way Flex works... I've been thinking > > about this sort of feature for a long time... If I knew about it before ( > > assuming it's not a bug ) I would have done this a long time ago... along > > with implementing other things like "deconstruct" etc etc > > > > monkey patching eh... never heard of it > > > > thanks Doug > > > > > > On Thu, Feb 21, 2008 at 7:19 PM, Doug McCune <[EMAIL PROTECTED]> wrote: > > > > > Just FYI, I posted an example of monkey patching FlexSprite to get > > > this functionality: > > > http://dougmccune.com/blog/2008/02/21/monkey-patching-flexsprite-to-list-all-event-listeners-on-any-flex-component/ > > > > > > Doug > > > > > > On 11/28/07, ben.clinkinbeard <[EMAIL PROTECTED]> wrote: > > > > > > > Gotcha. Maybe you should try sending cookies along with the request, > > > > I've heard it works well on the Flex team. :) > > > > > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, > > > > "Gordon Smith" <gosmith@> wrote: > > > > > > > > > > That would make sense, but it would be up to the Player team since > > > > > EventDispatcher is a Player class. The Flex team can lobby the > > > > Player > > > > > team for new features, but we don't get everything we ask for. > > > > > > > > > > Gordon Smith > > > > > Adobe Flex SDK Team > > > > > > > > > > ________________________________ > > > > > > > > > > From: [email protected] <flexcoders%40yahoogroups.com>[mailto: > > > > [email protected] <flexcoders%40yahoogroups.com>] On > > > > > Behalf Of ben.clinkinbeard > > > > > Sent: Wednesday, November 28, 2007 12:35 PM > > > > > To: [email protected] <flexcoders%40yahoogroups.com> > > > > > Subject: [flexcoders] Re: Am I the only one who wishes > > > > EventDispatcher > > > > > exposed its listeners? > > > > > > > > > > > > > > > > > > > > Why in subclasses and not EventDispatcher itself? > > > > > > > > > > Ben > > > > > > > > > > --- In [email protected] <flexcoders%40yahoogroups.com><mailto: > > > > flexcoders%40yahoogroups.com> > > > > > , "Gordon Smith" <gosmith@> wrote: > > > > > > > > > > > > > Does anyone from Adobe have info on why its not and/or if it > > > > might > > > > > be > > > > > > someday? > > > > > > > > > > > > The Player's EventDispatcher class doesn't provide this > > > > capability, > > > > > > probably because it isn't part of the Document Object Model Level > > > > 3 > > > > > > Events Specification. (The Player obviously keeps a list of > > > > listeners, > > > > > > but this is done in C++ code and the list isn't exposed in > > > > > > ActionScript.) However, I suppose the framework could accomplish > > > > what > > > > > > you want by overriding addEventListener() and > > > > removeEventListener() in > > > > > > every subclass of EventDispatcher to keep track of the listeners. > > > > > Please > > > > > > file an enhancement request at http://bugs.adobe.com/flex. > > > > > <http://bugs.adobe.com/flex.> > > > > > > > > > > > > Gordon Smith > > > > > > Adobe Flex SDK Team > > > > > > > > > > > > ________________________________ > > > > > > > > > > > > From: [email protected] <flexcoders%40yahoogroups.com><mailto: > > > > flexcoders%40yahoogroups.com> > > > > > [mailto:[email protected] <flexcoders%40yahoogroups.com><mailto: > > > > flexcoders%40yahoogroups.com> > > > > > ] On > > > > > > Behalf Of ben.clinkinbeard > > > > > > Sent: Wednesday, November 28, 2007 6:04 AM > > > > > > To: [email protected] <flexcoders%40yahoogroups.com><mailto: > > > > flexcoders%40yahoogroups.com> > > > > > > Subject: [flexcoders] Am I the only one who wishes > > > > EventDispatcher > > > > > > exposed its listeners? > > > > > > > > > > > > > > > > > > > > > > > > Sometimes it would be really nice be able to access a list of > > > > > > currently attached listeners by doing something like > > > > > > myButton.listeners. Having that return a collection of objects > > > > that > > > > > > expose the event type and handler method would be nice and it > > > > doesn't > > > > > > seem like it would be that hard to implement since they're > > > > obviously > > > > > > already kept track of somewhere. > > > > > > > > > > > > Does anybody else wish this was provided? Does anyone from Adobe > > > > have > > > > > > info on why its not and/or if it might be someday? > > > > > > > > > > > > Thanks, > > > > > > Ben > > > > > > > > > > > > > > > > > > > > > > > > > > >
