Alex, IMO, there was a huge necesity for the new spark component set due to multiple problems in MX. God methods with lots of mixed code and without ante separation of concerns that produces lots of lines of code, very poorly design that makes very difficult or impossible to extend the code, etc...Many of the problems comes was herency from code that was created in other time with less tecnique and knowledge. Today spark is much more usable and hope be complete so we can deprecate a obsolete MX code.
El martes 10 de enero de 2012, Alex Harui <aha...@adobe.com> escribió: > > > > On 1/10/12 11:32 AM, "Jonathan Campos" <jonbcam...@gmail.com> wrote: > >> >> I'm interested to see what ideas you have about a new skinning model. I >> like the way spark skinning works so I wouldn't want to lose that. But >> interested in what else there is. > I'm not sure there is "something else". The Spark skinning model is fine > (other than maybe it should draw the skin into the component instead of > being a separate display object). We could have retro-fitted every MX > component to instantiate a skin class just like Spark and not built up a > whole new component set, but there were additional goals around declarative > graphic primitives, MXML-only skins, and tooling integration that motivated > the decision to build up a new set. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > -- Sent from Gmail Mobile
