One last bit -- that's not to say we are not keen on adding such features in our controls. Quite the contrary. We are keen, very keen.
BUT, there is a long path that should be walked. For instance, most of the differences between classic and lightweight rendering are mere structural changes, but we still use the same class names. Those class names, unfortunately, are "scoped" to individual controls. For instance, if you have and arrow "component" in RadComboBox it would be rcbArrow, in RadEditor it would be reArrow, where as it's the same arrow.
The solution is pretty straightforward -- change the class names, use common abstract structures and things will workout.
So while the path seems clear, it's not quick / easy. Changing the class names / structure will make currently existing skins obsolete and practically useless. That's the same reason why skins for classic rendering will not work on lightweight and vice versa.
That's why we have built a new tool for skins called ThemeBuilder that can not only create skins for lightweight controls, but can also save the setting of the skins e.g. the color values that were in use. So in a later moment, if add something new, or change something existing, anyone can very easily import the settings back into ThemeBuilder and regenerate the theme.
So that's about it on different states of skins...
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items