Now that django is on github the best thing that could happen is to set it free and split it out as a separate django-admin repository that people can build on, and making site something like site = load_admin_site(settings.ADMIN_SITE) so that people can do drop in replacements. Not just that but splitting out the templates and static assets into a django-admin-originaltheme repository.
In this fashion projects like grappelli can proceed in an opinionated fashion on making changes to the admin as they see fit but remaining compatible with the ModelAdmin specifications, and django can pull back in the consensus commits. Grappelli does a lot of things right, but now I'm wanting to drop twitter bootstrap in on top of it, and tomorrow something else might be flavour of the month. 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. On Apr 29, 6:13 am, Idan Gazit <[email protected]> wrote: > As I wrote, I'd like to have a clear idea of what a new admin will accomplish > before starting to bolt on enhancements, even great enhancements like > grappelli. > > The admin was an impressively future-proof design, given that it is still so > useful years after it was designed. We should aim to make an admin that will > be relevant and useful five years from now; we can't design for that without > a couple of clear, simple goals. Grappelli may or may not align with those > goals. > > -I > > > > > > > > On Saturday, April 28, 2012 at 12:55 AM, Daniel Sokolowski wrote: > > On that note, why can't the fruits of Grappelli be used as a starting point? > > > -----Original Message----- > > From: h3 > > Sent: Friday, April 27, 2012 4:01 PM > > To: Django developers > > Subject: Re: Django Admin Revamp - Any updates? > > > I don't know the status of this project, but my guess is that you > > shouldn't hold your breath for it. > > > Fortunately, there is Grappelli: > >https://github.com/sehmaschine/django-grappelli > > > We are currently working on making it compatible with django 1.4 (see > > the "grappelli_2_4" branch) > > > Alternatively the branch on my fork works pretty well with 1.4: > >https://github.com/h3/django-grappelli/tree/grappelli_2_4 > > > Cheers > > > On Apr 26, 7:06 pm, Victor Hooi <[email protected] (http://gmail.com)> > > wrote: > > > Hi, > > > > Is there any news on the Django Admin rewrite front? > > > > I remember around a year ago, there was quite a bit of talk on revamping > > > the Django admin UI - I think Idan Gazit was heading that, right? > > > > Is that still on the Django roadmap? Any idea of whether it'll be in 1.5, > > > 1.6, 1.7 etc? > > > > Cheers, > > > Victor > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django developers" group. > > To post to this group, send email to [email protected] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:[email protected]). > > For more options, visit this group at > >http://groups.google.com/group/django-developers?hl=en. > > > Daniel Sokolowski > > Web Engineer > > Danols Web Engineering > >http://webdesign.danols.com/ > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django developers" group. > > To post to this group, send email to [email protected] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:[email protected]). > > For more options, visit this group > > athttp://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
