BTW, the URLs http://blog-amirouche.dotcloud.com/notes/2013/admin-next-a-new-api.html http://amirouche.github.io/blog/django-admin-next-a-new-api.html lead to 404s.
The correct one is http://www.hypermove.net/notes/2013/admin-next-a-new-api.html On Saturday, March 30, 2013 5:49:27 PM UTC-5, Amirouche Boubekki wrote: > > > 2013/3/30 Victor Hooi <victo...@gmail.com <javascript:>> > >> heya, >> >> Aha, yes - we need a roadmap, and somebody from the team to execute it >> *grins*. >> >> For the former - I believe there was already discussions on that sort of >> thing on this board? >> >> There's a wiki page with some notes as well: >> >> https://code.djangoproject.com/wiki/AdminNext >> >> I also had a look at some of the existing projects: >> >> - https://github.com/yawd/yawd-admin >> - https://github.com/michaelhelmick/django-bootstrap-admin (Doesn't >> appear to be too active) >> - https://github.com/riccardo-forina/django-admin-bootstrapped >> - https://github.com/aobo711/bootstrap-django-admin >> - >> https://github.com/gkuhn1/django-admin-templates-twitter-bootstrap(Doesn't >> appear to be too active) >> - https://github.com/divio/djangocms-admin-style >> >> And there's obviously Grapelli. >> >> A lot of these are obviously just reskins, while others offer a bit more. >> >> From the existing projects, we can draw two clear requirements that >> people want: >> >> - Changing the look and feel - I'm not sure what Django core's >> feelings on it, but there seems to be a feeling from the community that >> the >> look of the current Django Admin is somewhat dated? Also, any new admin >> should probably be responsive, and work on mobile or non-desktop devices, >> if that's possible. >> >> > This question leads to another should Django develop its own css framework > and re-use existing one, if Django use an existing one, Django must make it > easy to work with the preprocessor. While I liked much bootstrap, > foundation's mobile first approach of Foundation is appealing even if more > verbose. > > >> >> - More customisations - a lot of people want to create dashboards >> around the admin, add new sections/tabs, or move things around - the >> current Admin doesn't have much scope for that, or it's not easily >> accessible. >> >> Those are all things that are doable right now. I though it was about > something more «disruptive» that's why I called the page AdminNext to > follow the naming of next html version... whatever the naming, the goal > should be the same aka. not only a cbv-Admin which should only adress the > customisability (and readability) side but add features. This lead me to > the group/permission-centric admin which creates menu based on permissions, > but I did not implement it. I've documented a sketch API [1], but I'm not > very happy with it, I'm now thinking about something in the spirit of > lettuce to create an admin. > > I stopped working on the composite admin because a) the composite thing is > too much b) I wasn't confortable with the code handling inlines in current > admin so I started thinking about fixing it but got stuck (!). > > Also there is this conversation that is somehow related: > https://groups.google.com/forum/#!msg/django-developers/wI18E6BZImQ/TS2wSvUCkaAJ > > Maybe Django should gather money somehow and tell a company to do the job > instead of relying on the community ? > > HTH, > > Amirouche > > [1] http://amirouche.github.com/blog/django-admin-next-a-new-api.html > > > >> For the latter, not sure I can help you there...lol. I thought Idan Gazit >> was working on something before though? Or are there other designers on the >> Core team? >> >> Cheers, >> Victor >> >> On Sunday, 24 March 2013 22:14:58 UTC+11, Russell Keith-Magee wrote: >> >>> >>> On Sun, Mar 24, 2013 at 6:20 PM, Victor Hooi <victo...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I read recently about Andrew Goodwin's successful kickstarter project >>>> for better Django schema migrations: >>>> >>>> http://www.kickstarter.com/**projects/andrewgodwin/schema-** >>>> migrations-for-django<http://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django> >>>> >>>> Kudos to him for awesome work on South so far a swell =). >>>> >>>> There doesn't seem to be much movement on the Admin front - >>>> https://groups.google.com/d/**msg/django-developers/** >>>> Vozu6U3gz84/vvbTqrWitxIJ<https://groups.google.com/d/msg/django-developers/Vozu6U3gz84/vvbTqrWitxIJ> >>>> >>>> I'm wondering - is there any impetus for a similar kickstarter for the >>>> Django admin? >>>> >>>> I for one would be willing to put my money where my mouth is and back >>>> it - and I'm sure other people/companies who use Django in their own >>>> projects would as well. >>>> >>> >>> Good to hear :-) >>> >>> There's one significant difference here. Andrew's project was to deliver >>> South-like functionality to trunk. South is a known quantity, and there >>> have been discussions and threads about exactly what merging South into >>> trunk would look like. And on top of all that, Andrew is the principle >>> author of South, so he's well positioned to do the work. >>> >>> What's the feature set for a new Admin? What are the design goals? And >>> most importantly, who is going to do the work? >>> >>> I'm not saying these questions can't be answered -- but the answers >>> aren't clear at the moment (at least, not to me). Once we've got a clear >>> plan, and someone who is available to deliver on that plan, then a >>> Kickstarter might be appropriate. >>> >>> Yours, >>> Russ Magee %-) >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to >> django-d...@googlegroups.com<javascript:> >> . >> Visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
