I've been poking around the contrib.admin CSS recently after a long
hiatus. I'm amazed at how well they've held up all this time, but
obviously after three years I've changed my mind about some of the
bright ideas I had when I wrote the first version.

Obviously, with newforms admin it's a lot easier to customize the
admin, but the admin CSS still has some quirks that make it less than
hospitable to customization and reuse.

I'd like to make some changes to improve that.

Goals:

1. Make the admin CSS files easier for multiple editors and more
version-control friendly
2. Reduce unnecessary complexity of the admin CSS file structure
3. Replace obscure CSS parser hacks currently used to filter CSS for
IE
4. Encourage reuse of existing admin styles in custom app admins

Implementation:

1. Reformat admin CSS to use multi-line selector format instead of
single-line selectors. Easier for multiple authors to get in and
understand what's going on, and much better for tracking changes in
version control, since each rule is on it's own line.
2. Combine most (all?) of the admin CSS files into a single file and
cut down on (remove?) @import rules. The current file structure has
different components separated into different files, which import each
other. It's too complicated to figure out what's going on, and the
extra HTTP requests aren't necessary for the debatable benefit of
having separate files for everything.
3. Use IE conditional comments to block the admin CSS from IE5 and
serve the patch file with fixes for IE6. Much more consistent,
reliable, and easier to understand than the current parser hacks.
Also, can finally get rid of that stupid null.css file.
4. Refactor some admin styles (form controls, button styles, etc.) to
make them easier to reuse.

Obviously these are pretty minor changes, and shouldn't affect the
appearance or function of the admin at all. But I wanted to put it out
there and get a feel from the rest of you folks what impact these
changes might have on any existing admin customization projects out
there.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to