On 15 Jan 2012, at 21:54, Jeffry Houser wrote:
That is kind of what the Spark Architecture did. And the end
result is that development is more complicated to extending and
modifying things [from the perspective of a component developer] is
a complete nightmare. It's much worse than the "too many private
variables" problem that existed in the Halo architecture.
For the sake of simplicity in development; wouldn't the MX approach
of having a single class to represent the List be better?
In my view Spark favored flexibility over simplicity.
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
I much prefer the code base of the Spark List as a user and component
dev.
Scroller, DataGroup and skinning opened up so many more possibilities.
Those privates still get in the way though!
Please lets not go back to the MX days!
Tink
