>Does the roadmap for the FlatSpark includes providing a way to skin all UI components of Flex?
Yes, we are designing it with the option to change all the skins at once, if wanted by the developer. > Regarding the FlexJS + Flex sharing the same theme, I was rather on the > "design" and artwork level, rather > than the implementation. > But maybe there is something to do at the implementation level too, or > even the compiler. > I thing we will see when starting working on it. I agree, we also meant on the design level. We are not familiar with the way FlexJS work internally right now, so I guess we should talk about how this could arranged so the portability to FlexJS can be more smooth. We are defining skins primarily for the Spark components, but we also have some custom components. For example, we have ButtonSkin (which uses Spark), but we also have ButtonIconSkin (custom component), which inherits from Button but has custom parameters, like an FontAwesome (which is a dependency) text to render it as an icon. What you think about these custom components (ToggleSwitch, TextInputIcon, etc.)? They are not default Spark components right now (at least not on the web version). Should this be separated as some kind of "extensions" or would this be incorporated too? ----- Skype: muddibr -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Use-FlatSpark-as-theme-for-FlexJS-tp37721p37738.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
