jannis (leidel) asked me to join this thread in order to add some comments.
we´ve been doing grappelli (http://code.google.com/p/django-grappelli/ wiki/screenshots) for a while now. grappelli initially should be a "skin" for the admin-interface. while working on it, we´ve had issues skinning the interface and maybe it´s helpful to point out some of the main problems. currently (from what I´m seeing) there are new features planned (or already integrated) with the admin-interface. that´s nice. but (IMHO) the HTML/CSS needs to be refactored as well. I´m not talking about colors are fonts, I´m talking about some kind of html-css-framework for the admin-interface. so, here´s our proposal: http://vonautomatisch.at/grappelli/ (sorry for the strange navigation) PLEASE NOTE THAT THIS IS JUST A DRAFT AND SOME THINGS ARE BROKEN. we ´ve already been integrating most of this with the next version of grappelli (the above site is about 2 months old and there´s already been some changes). therefore, we´ve stopped developing the above site ... the most important change is probably the introduction of an overall grid, see: http://www.vonautomatisch.at/grappelli/basic-document-structures/grid-based-on-blueprint/ http://www.vonautomatisch.at/grappelli/forms-in-container-grid/basic-form-elements-in-container-grid/ moreover, we´ve tried to refactor all javascripts with jquery, see: http://code.google.com/p/django-grappelli/source/browse/#svn/branches/haineault/media/jquery/grappelli/src (done by maxime haineault) as already discussed with jannis, what I´d like to see with the admin- interface is a solid and comprehensible structure as well as coherent styles. based on this, different "skins" are easily possible. I don´t wanna be to detailed right now, but there´s too much hardcoded stuff with the current admin-interface and the admin index page could benefit from some changes as well. here´s an (outdated) list of issues: http://code.google.com/p/django-grappelli/wiki/djangoissues let me add a note about the "contest": if it comes down to skinning the admin-interface, a contest is not needed from my point of view. if (one day), it´s easy to "skin" the admin-interface, different skins will evolve (e.g., grappelli). I think that it´s important to create the prerequisites for skinning first. regards, patrick On 6 Feb., 13:18, Luke Plant <l.plant...@cantab.net> wrote: > On Saturday 06 February 2010 09:07:33 j...@jeffcroft.com wrote: > > > To expound, it seems like you guys are thinking of a re-skinning. > > I'm not talking about a re-skinning. I'm talking about a complete > > re- thinking of the admin interface. By 1.2? Not a chance. By 1.3? > > Maybe. But I wouldn't count on it. I'm talking about bringing the > > admin to 2010, just like you all brought the models API current > > after .96. Seriously, what if the models API hadn't changed in > > five years? Do you think it would be a small project to bring it > > current? Of course not. It would be huge. This is a serious > > undertaking, and the idea of doing a "contest" feels like you > > think it's a commodity. This is a serious project for serious > > designers, not a g'damn reality TV show. > > The original thread seemed to be about re-skinning at most ('refining > Django admin look'). The choice about whether it goes in is largely > down to a matter of taste and aesthetics, which is why our normal > procedures with tickets and feature voting really wouldn't work - for > an aesthetics 'bug' you can have multiple 'fixes' which are all > 'correct'. To avoid pointless debate, a contest seems like a good > idea. Personally, even a re-skinning brings with it potential design > problems for existing installations, so I'd have to be convinced the > re-skinning was a big enough improvement to make up for that - I agree > with Russell that this definitely isn't something we should be doing > every few months, or even every year. > > If it's a complete re-thinking of the admin interface, it's obviously > a much bigger undertaking, and brings with it huge implications in > terms of backwards compatibility. Even if just the templates were to > be re-worked, we have to consider all the people who have custom admin > templates that assume the current block layout etc. A bigger re- > thinking of the admin would involve even more changes to code. > > The models API change that occurred after 0.96 also occurred before > 1.0. There have been very few breaking changes to it since then (have > there been any in that department?). > > Like Alex, I must have missed a lot of messages to this list if a > major re-thinking of the admin like this has been repeatedly proposed > and dismissed. And it's kind of difficult to assess what is currently > an extremely vague proposal. > > Luke > > -- > "Whom have I in heaven but You? > And there is none upon earth that I desire besides You." Psalm 73:25 > > Luke Plant ||http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
