Some thoughts about Flex DataBinding code generation:
Binding was considered a performance problem in Flex and every time I looked
into it I came away with the idea that by having a better component lifecycle
and different kinds of binding instances that are smart about the lifecycle
and
Re: fx:Declarations.
I don't recall the exact reasons why that happened in Flex 4. It might have
been for Spark Skinning where the children have to be passed down to the skin,
but it might have been a performance optimization where an array of children is
built and passed to the skin and not
I will be doing some other comparisons with Flex soon for Bindings, so I
might be able to do that actually. I will probably just create an issue and
note things down if I do that and only come back to them later.
I did work on something for bindings related to the needsEventDispatcher
stuff
OK, thanks for figuring it out.
I'm not familiar with this scenario at all. My main goal was to debug the data
stream since most folks aren't familiar with it.
It is true that, currently, to be an MXML tag you have to implement certain
methods. Maybe that will change someday based on what
This is related to compiler changes following a specific request in users
list.
Changes were made to the compiler to help cairngorm ServiceLocator work
in mxml.
@aharui :
there was a change that added the following to an mxml subclass of
ServiceLocator in a local test project
