The new skinning architecture in Flex 4 separates business logic and design for a component. The component itself contains only the functionality (the M and C of the MVC pattern) and the skin defines its visual aspect (the V of MVC). If used correctly, you can change the design (skin) of a component without the need for changing the code of the component itself. One component and many skins, e.g. for desktop, for mobile, for different applications.
Skinning is very good documented and there are many resources available, just search for "spark skinning". Haykel Ben Jemia Allmas Web & Mobile Development http://www.allmas-tn.com On 9 February 2012 18:07, Davidson, Jerry <jerry.david...@illinois.gov>wrote: > ** > > > I think the skinning allows the components to be lighter. But it makes > everything a lot more complex.**** > > ** ** > > A month ago I started a thread on what the pieces in a skin mean and not > one person was able to respond so there seems to be a learning curve at > work.**** > > ** ** > > *From:* flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] *On > Behalf Of *Myadi H > *Sent:* Wednesday, February 08, 2012 10:33 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] Advantages and Disadvantages of skinning**** > > ** ** > > **** > > Hello folks, > > Today I have been asked to explain advantages and disadvantages of > skinning in flex. I thought of asking this to all experienced flexers, and > here it is. > > I hope this discussion will help everybody in future. So please > input/share your knowledge. > > Thank you.**** > > **** > > >
