> I think that a very small amount of plumbing, all using standard pivot idioms > (which means none of my usual tricks) could create simple templates for > components. If a look at TabPane, tab button creation is buried in the skin.
This is actually by design. We did it this way so that the skin can decide how best to implement itself. We don't want to impose too many assumptions or restrictions at the Component level. > You could also write a new skin or an extension of the skin (although with > the creation and instantiation buried in the skin, it's still hard to > override). Components in Pivot are meant to be overridden, but the same isn't necessarily true for skins. Where applicable or beneficial, yes - but skins are often part of a theme, and a theme is a consistent unit that, aside from style properties, is largely transparent to an app developer. So we haven't generally designed the Terra skins for extensibility except within the theme itself. > At the very least it would provide a contrasting implementation around 570. True, but the proposal in PIVOT-570 would make TabPane and Accordion more consistent with the rest of the framework, which is nice.
