Styling admin in place

[psoTFX]

The M-2 styling system is now in place in CVS ... I'd appreciate feedback on it. How useable it is (or isn't), what's missing (that isn't described below), what doesn't work as expected, etc. I'm not looking for comments on the templates themselves or what the template system does or doesn't do. This is just about the admin styling setup.

To be added during M-3 will hopefully be:

• Ability to replace/update an existing stylesheet, template, template set and imageset.
• Possible capability to replace single images in the imageset or theme
• Possible online help but at least an online guide to available vars in a given template
• Manipulation of existing and admin defined BBCode templates

Things to remember when using the Style ACP functions:

• Safe mode is a nuisance to say the least If you have safe mode enabled wave bye bye to the upload and import capabilities (though you can still edit templates/themes online).
• If you have file uploads disabled wave bye bye to being able to upload anything.
• If you don't give world writeable access to the style/ directory wave bye bye to upload/import (though as with safe mode you can still edit templates/themes).

Things to note

• Remember to submit changes made in the template, imageset or theme editing forms before selecting another entry to edit! For example if you edit the "Body" class in a theme hit submit before selecting another class. Changes are not saved between changes in class (or template or image). To do so would IMO cause more trouble that it would solve in the long run.[/b]
• When creating a new style I recommend you do so using the basis feature. That way you'll have somewhere to start ... rather than trying to create an all new style which will at best only partially work.
• Remember to use the export feature when saving out style elements or styles ... exported themes will include the necessary cfg file allowing importation/installation on someone elses system.
• When exporting a style be mindful of exactly what you are exporting. For example it's a given that the vast majority of users will have the subSilver style installed. Thus they will have the subSilver template, theme and imagesets. So if you are using one of these in your style it is probably not worth exporting that element ... this will reduce the size of the archive and increase compatability.
• Name new elements or styles uniquely ... the styling system relies on unique naming to minimise duplication.