AMamirouche·Jun 18, 2013
> I don't know about that.
1) (minor) Getting into templates to add an action e.g. «export as CSV» is a lot to ask. (Anything that leads me into changing the templates is, at least for me, a no, except form ergonomy which is in Django regularly done in an API/DSL based on nested dict, list and attributes.)
2) (minor) Custom models (non django.models.Model) or specifiq models (like django scaffold) in the ObjectList aka. ChangeList or in the Form view is not possible which means no mongodb, no kv store, no to anything that hasn't a proper Django's model backend even if in the end it's all about class properties and most of the time slice queries.
3) (major) The admin ergonomy and plugability is poor, you can not choose the way pages feet together, for instance and the primary concern is that the first page must be a list of models regroupe
Read the rest
d by apps. This is in advanced apps a non sens, most likely when you use a lot of reusable apps, where the code doesn't reflect the end-user experience, the admin will look ugly. But should the admin reflect or map somehow the end-user experience ? It's a complex mapping, the workflow of the admin is elaborate and depends of the app... otherwise said the Django «generated» admin is the equivalent of a spreadsheet compared to specific domain admin areas.
> I've customized the heck out of that thing (e.g. https://github.com/mazelife/django-scaffold)
Does it support filters and actions ? because what it looks like you did is that you are feeting a view to the admin API, leaving the elaborate actions and points of customisation on the side.
> and it's quite possible,
It our job to make things possible.
> although you'll need to be pretty familiar with the source code.
You mean read the code ? It's not that difficult. Also I think django admin reworks bring more clarity.
> That said, this particular part of Django is definitely starting to show its age.
In terms of features or skin ?
> Compare the look-and-feel and UI with something like ActiveAdmin (http://activeadmin.info/) for Rails and you'll see what I mean.
Definetly looks like a customised Django Admin. Also Django Admin already had it's skin war, the feature/API war is barely starting.
> What's more, the approach to "class-based views" feels disconnected to the way Django apps are written now.
What do you mean ?