What would be the value in replacing the admin with a new version with abstracted, reusable tools... that still resides in the new admin? IMO, duplicating the admin's features would be better than that (assuming you can't simply change the admin's guts in-place, which is probably the case).
On Oct 10, 9:04 pm, tWoolie <[email protected]> wrote: > > Yep. Could you outline your plan of attack for this? > > 1) create "newadmin" project to be a dropin replacement for admin. > (Clone current admin and slowly replace features/trim dead code) > > 2) Split out filterspec functionality into newadmin.filter. > - Give it a nicer wrapper such that a FilterSet can be declared and > instantiantiated much like newforms > - Move API for registering filters out of ModelAdmin and into > newadmin.filter > > 3) Split out table generating/sorting/display into newadmin.table > - clone django_tables2 and do some refactoring as necessary > - replace admin functionality with admin.table functionality > > 4) Develop CBV Wrappers for the core functionality > - replace admin views with CVB style views -- 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.
