On Mon, 2004-06-12 at 15:12 -0800, Brion Vibber wrote:
Now, perhaps we could get rid of even that, but it's most of the way there. What actually needs to be different?
Uh... didn't I just send a great big email about that? B-)
The upshot was: not much. It's really pretty good right now, as I noted before. But I think it might be easier if you could say:
$wgDefaultStyle = 'supercool';
or:
$wgStyles = ['supercool', 'sputnik', 'razorback', 'friedegg'];
If I'm not wrong, the class declaration for the Skin inherited from Monobook has to be in its own file in a certain place and have a certain name. Or you have to write some more code to inject it into the list of available skins.
I think the main thing that bothers me is that we (dev group) keep turning away people offering to do new designs. We say, "Well, you have to make a subclass of SkinPHPTal, then a new Tal template, then...". Yes, I know it's not that way any more, but I think if we can say, "Make a CSS stylesheet for this sample HTML", we can get a wider variety of style and interface, like at the CSS Zen Garden:
I had a couple of other major points: about subsuming our current skins into the same Skin subclass as Monobook, using CSS for them; about pushing the functions that make the menus up to the root Skin directory; and a couple others.
~ESP