On 1/10/12 3:36 PM, "Michael Schmalle" <m...@teotigraphix.com> wrote:
> Hearing this from you now it would explain why in the beginning the
> Spark set was small, lightweight and manageable and then all the
> sudden the classes got huge and out of control.
I would say it wasn't because of an agenda per-se. IMHO, the issue was we
hit performance issues because we weren't able to build Spark from the
ground up. It was living on top of UIComponent. It is hard to run fast
when you put on heavy shoes.
So then MXML-only skins started having AS added in. Instead of using
binding we developed a complex skin-part mechanism.
In one of my first posts, I mentioned that we are working in a constrained
environment. It is hard to execute good theoretical architecture.
Sometimes, you even have to cheat. This will be true in my whiteboard
project. There will be some cheating going on. The key will be finding the
right way to go about it.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
