Gabriel Wicke wrote:
On Thu, 2004-09-02 at 03:49 +0200, Ashar Voultoiz wrote:
Once my code is finished, skin designer will just have to zip a tree like: / -- skinname.php // php class -- skinname.xml // PHPTal template
I think it would be desirable to be able to add more skins based on the same template easily, without re-adding the xml template or a class. A css/picture dir and the skin name added to an array could be enough.
The idea behind the heavy use of css was mainly to avoid having many templates, and to have a mainly structural xhtml that's as decoupled as possible from the actual appearance. Makes maintanance probably a bit easier and helps with future improvements to the caching system.
I fear that skin designers would be tempted to simply modify the xml if it was mandatory to add a per-skin template anyway.
But then, the caching scheme isn't implemented yet, so it doesn't matter that much currently. Could be hard to reverse though. I found it interesting to see that the website of the athens olympics was ESI-based as well, shows that it's not too exotic technology.
Hello Gabriel,
My idea is to allow non-wikipedia site admin to create new skins easily and share them.
For wikipedia caching issue, we could set a skin white list / delete unwanted skins.