I agree with Idan. We mainly did Grappelli because of the look & feel (and then added some functionality like autocompletes).
However, it just doesn´t make sense to simply "beautify" the existing admin-interface. Rethinking the functionality, adding flexibility, being able to customize ... these are all necessary steps IMHO, but I´m still missing a clear approach/roadmap on how/when this should happen. I planned to give a talk on djangocon.eu about how to improve the admin-interface. Unfortunately, I had to step back from that idea because of some customer-related projects. Still, the thoughts are there and I´m happy to discuss this issue anytime. This discussion could start with defining the so-called "trusted editor" – what does he/she knows resp. needs to know when dealing with the admin-interface? What are the consequences (e.g., does an editor care about an app-list, does he even know what it is)? What working-groups do we need (python, html/css, js, ...)? How can we publish the process/discussion? And much more ... let´s start ... but how? best, patrick Am Montag, 30. April 2012 23:41:14 UTC+2 schrieb Idan Gazit: > > > > On Monday, April 30, 2012 at 10:16 AM, Brett H wrote: > > > Increasing the flexibility for development and integration is more > > important than trying to 2nd guess where we are going to be in 5 years > > time. > > Fair enough, but that sort of flexibility is available now. Nothing is > preventing you from starting your 3rd-party admin app today. > > > > The issue is Django's officially-blessed, officially-documented admin. I'm > not sure it's better to have admin in contrib (or contrib at all, but > that's a separate ball of wax). I have a feeling that this issue will > probably be addressed once again now that we're on github. > > All the same, if there's going to be an official django admin, I'd like it > to give some thought to the issues I've raised. I have no problem (read: > would love) to draw upon existing solutions for an admin revamp, but right > now I don't have a fitness function to guide my decisions, and I think that > is necessary. Not a spec, just an attempt to step back and think about what > the admin should do. > > -I > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/J5836To_XtkJ. To post to this group, send email to [email protected]. 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.
