Bugzilla CSS plan

[Myk Melez]

Ludovic Dubost wrote:

> I like it.. especially since this seems close to what I did in the 
> patch in bug 69654.. It seems to be 251068 is a duplicate of 69654..

Actually, part of it is a duplicate of 240486, which has been fixed.

http://bugzilla.mozilla.org/show_bug.cgi?id=240486


> One thing that could be interesting is to link the use of a non 
> default CSS directory to a non default Template directory.. Sometimes 
> skins need to have modifications in the templates.
> Also the skin directory should allow for use of images and javascript 
> files which are necessary of user interface customization not possible 
> in pure CSS.

We should definitely support images.  I'm not keen on expanding the 
definition of "skin" to templates and JavaScript, especially given the 
way we've overloaded templates for localization (although this could be 
fixed by separating localizable strings into blocks in a separate 
template file), but I also don't want it to be prohibitively difficult 
to achieve in the future should we find it useful.  One way to prepare 
for that possibility and handle images better at the same time is to 
break skin directories into constituent parts by file type, i.e.:

skins/<name>/styles/
skins/<name>/images/
skins/<name>/templates/
skins/<name>/code/

Another way is to put files of all types into page-specific 
subdirectories, i.e.:

skins/<name>/index/
skins/<name>/query/
skins/<name>/buglist/
skins/<name>/bug/

Of these options, the latter seems more sensible.

> Finally, it could be interesting also to allow in each skin, multiple 
> alternate stylesheets which would need to be declared somewhere (in a 
> text file in the skin directory - this seems the more logical solution 
> - or in the bugzilla params or in the user preferences).

This sounds overcomplicated.  I'd rather just have installations install 
multiple skins.

-myk