> > IMO, a pain point in Flex was that styles had to be specified on the > component when the style implementation was actually in the skin/theme. > The skinning model is different in FlexJS anyway so I think that gives us > license to change the styling model as well. If you ever set a style on a > Flex component that wasn't in your custom theme, or tried to add a new > style to a skin/theme that wasn't declared on the component, then you know > what pain I'm talking about. > >
Absolutely. Some time ago I was writing about this on the list: "... this make me think about a limitation see with current Spark skinning implementation: the relation between skins and styles. Sometime it would be useful to "configure" some skin visual properties directly from MXML using a style, but style must be declared by the host component (even if inherited by the skin, think about "borderColor" and "borderAlpha"). This force you to subclass and/or create a strong dependency between component and skin (leading to "theme warnings", such as "the style XXX could only be used with theme YYY"). My current workaround is to use CSS rules to assign styles directly to skin classes, but its far from perfect.." I didn't have the chance to see if the FalconJS skinning model overcome this issue, is there some wiki page or thread explaining the approach? Thanks, Cosma
