CODEWITHSUNDEEP
apache-flexcustomizationflex4.5skinningflex-spark
Mansuro
Mansuro

Reputation: 4627

flex skins or style?

I made a research, but I didn't find anything to helps me answer this question

When you have a flex project, is it better to use different skins for different components or to use just one big css that has all the styles together?

Upvotes: 0

Views: 265

Answers (1)

Constantiner
Constantiner

Reputation: 14221

It is not very clear from the question are you talking about standard components and their custom skins/styles or you're talking about custom components and ways to design them to be customizable?

Anyway I'll try to answer. Spark architecture isn't reject styles and using CSS for component's customization. All the standard components support styles and have out-of-the-box skins which support them. So if you're using standard components with standard skins and it fits your requirements it is better to use available styles for additional customization.

If standard skins of standard components don't fit your needs you have to decide which strategy to choose:

  1. Create skins which support additional customization with CSS. You can choose this option if you're creating some skins for external use (for some other developers or teams). It gives them possibility to use your skins without modification and with additional customization. If you're creating custom components for sale or for a client you also should choose this strategy.
  2. Create skins without additional customization possibilities (all the values such as colors, icons, fills, strokes, fonts are hardcoded). This is the easiest way to create skins. And it allows you to perform skin's modifications easily. You should choose this options if you're creating skins for the particular project with particular look and feel. The main advantage is you can create and modify skins very simple and fast with more flexible usage of external tools such as Flash Catalyst.

Upvotes: 2

Related Questions