> I think it's a good idea but I'm not sure how this would differentiate > pivot
I just thought it might be a quick-and-dirty way to add native L&F support to Pivot, since at least one developer was asking about it. I'm not sure if it it is a good idea or a bad one - just wanted to put it out there for the sake of discussion. > typical "skin" attributes such as colors and other things may need to > migrate back to the model instead of the skin to ensure that they are > available in all "rendered" versions of the skin The styles wouldn't need to move to the component level. The skins would simply delegate the style properties to the underlying native components. This is actually a good example why we designed the styles API the way we did: not all themes (native or otherwise) can be customized the same way and can't realistically support the same set of styles. This is OK, though - a developer who wants complete control over an application's appearance probably wants to use a cross-platform L&F with lots of customizable styles. A developer who wants an application to appear "native" on all platforms probably isn't going to do much, if any, style customization, since that might produce a UI that looks inconsistent compared to other native apps. G
