On Saturday, April 28, 2012 10:13:03 PM UTC+2, Idan Gazit 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. >
As I just blogged: "Last year, I sent a letter to santa asking for 12 transformers with super laser powers. I waited nicely and then received a little playmobil." A couple of "clear, simple goals", you ask: 0. Loose coupling goal The new admin app should not include ChangeList (ie. django-tables2), form rendering (ie. django-floppy-forms), queryset filtering (ie. django-filter), etc, etc .... 1. KISS goal The new admin app should not try to abstract the basics of Django elegant design. Instead of: admin.site.register(Foo, FooAdmin). I could use: url(r'myapp/foo/', admin.ListView.as_view(table=FooTableClass, filters=FooListFilters), name='myapp_foo_list'). Of course, I could use a shortcut / factory / something cool. But the new admin app would be so simple I wouldn't need ModelAdmin and I could override anything easily and I could even reuse parts of it in my own views (see "Loose coupling"). Hope this helps. -- 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/-/8oNVlVMOya4J. To post to this group, send email to django-developers@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.
