On the whole, what Aexoden said.
But to address some specific point asked by Paul:
psoTFX wrote:How far should we go in transfering basic conditional statements from he source to the templates? e.g. row colouration, limiting output of content not applicable if not logged in, etc. etc.
I think this would be a good move. Despite the fact there would potentially more contitionals within the templates, and making them a bit more "code-like", it does mean that template changes are abstracted and completely contained within said HTML files.
One wouldn't have to go poking about with core code to change things.
I know Paul's concern would be that this would affect performance too much, but since templates are already cached, this would only be so for the "first pass"?
Guess some benchmarks on moderate to heavily loaded servers?
What needs to be moved from the source to the templates/style/imagesets? What needs to be moved back?
The only thing I can think of right now would be the image sizes being defined inline with the image URI within the DB.
Do we need the image sizes anyway? As the height/width attributes can be defined using HTML attributes or via CSS (classes or inline via style="")
People may use the same imageset across a number of templates, but in such cases, it's image dimensions will be the same, so sizes can be hardcoded.
If people want to use different imagesets, I can't see any reason why they would make said images the same size as their alternate anyway.
psoTFX wrote:How should we handle theming? i.e. completely freeform css with minimal/no essential [ source required ] classes? Basic set of "pre-defined" classes supplemented with freeform data? Something else?
Pity CSS2 is still poorly implimented in a certain browser, otherwise it'd be possible to style a table and all it's contents just by assigning a unique id to it, no more stupid classes per td or whatever.
But anyway, CSS isn't that hard, and there are a good deal of tutorials. People typically just want to edit colours.
psoTFX wrote:Are we handling imagesets in the right way? If not, why not?
I think we are, but I'm wondering if being able to "mix-and-match" a number of image sets be useful? Say one set of images had dark BGs, and another light BGs. One way want to be able to pick and choose depending how dark said area of the template was for that "area".
psoTFX wrote:How should the admin controls for styles be arranged?
Need to think about thes, but I don't see any major problems.
But as Daz noted, an external CSS file needs to be "accessible", say putting it into ./cache/templates/templatename/whatever.css, as it appears from other peoples experiments, a PHP generated CSS file doesn't work very consitantly, but it could be specific browser/server set up issues.