Hi, Maxym. I'm sorry that you're unhappy with the
design of the event system in Flex. However, we believe that it's usable,
high-performance, and follows a standard. I'm sure there are ways it could be
better, but we won't be changing it -- at least for this release! -- as the
product is already at Beta 2. - Gordon From: Yeah, I can. DOM Specification: The first goal is the design of an event
system which allows registration of event listeners and describes event flow
through a tree structure. TREE STRUCTURE. So can you explain me why Timer extends EventDispatcher.
Can you imagine TREE STRUCTURE of Timers??? For real there are many bad things in this
event model: 1. It’s based on string identifiers. Because of this a. It’s slow b. You don’t know for real types of events that object can
dispatch. c. You can’t use code-inside in editor for access events. 2. EventDispatcher and IEventDispatcher have too much extra
functionality that will be used only for visual objects. 3. If you want to dispatch events and you can’t extend
EventDispatcher you have to duplicate (do you know some AOP concepts)
it’s logic (at least one time) and implement IEventDispatcher. 4. I can say more but I’m tired of typing… From: maxym.hryniv wrote: |
- Re: [flexcoders] Re: Question to Adobe about Flex Framewo... Darron J. Schall
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Maxym
- Re: [flexcoders] Re: Question to Adobe about Flex Fr... Peter Hall
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Gordon Smith
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Ted Patrick
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Ted Patrick
- RE: [flexcoders] Re: Question to Adobe about Fle... Gordon Smith
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Ted Patrick
- RE: [flexcoders] Re: Question to Adobe about Fle... Gordon Smith
- RE: [flexcoders] Re: Question to Adobe about Flex Fr... Ted Patrick