It is experimental, though, so it's ugly coding for now, but I did manage at one point to do a "#id reset extends something" which I thought was pretty neat :D
I felt the same, made the same for Wine when rewriting inheritance, but I had to get rid of it and it broke my heart. Good that you could add it, so it'll give an example to future skinners
:)But it is also interesting to note where there is styling stuff hardcoded - the gap between the catbg and the titlebg bars in the screenshot is not controlled by the theme - but by a hardcoded div in the template.
Really...? Is that something in Wedge you mean? Where?
You can rewrite title headers with a mixin, although I think they really need some kind of rewrite... (Perhaps just removing the default ones from the index template, because it's really not the same format as in skin files.)
Interestingly, it's not possible to truly replicate SMF's Core layout without changing templates, because there's no way I could find to wrap both the upper sections (the blue gradient area, the title area) with the navigation menu inside a single element, to get a border around both at once, because they're contained in two separate divs and the only parent is #wedge which contains the entire page.
Everything is doable in CSS...
:niark:Just that sometimes it's not worth it.
Posted: February 24th, 2012, 03:59 PM
Speaking about the skin system...
I was thinking about something a bit funny and idiotic. And very certainly too late in the process.
Having all template blocks behave as if they had no indenting at all, and then indenting them when outputting them, by using the number of tabs by which the block name is indented in the skeleton.
The code is already ready for that, since there's an 'indent' param in skeletons, I just thought it'd be neat to do it automatically based on the skeleton...
Of course, the only (and major!) issue is that it would require going through all existing templates and removing their base indenting.