Hi Iván, I'd temporarily given up on getting extra_views into Django because of a blocking issue with pagination and formsets.
Assuming a goal is to be able to build a new admin using class-based views, there is a prerequisite of being able to paginate, sort and filter on the querysets used for modelformsets. The problem is that with Django's class-based views as they are, pagination is handled at the template context stage of the logic, whereas the formsets are instantiated and validated much earlier. I had raised a ticket about fixing this, but it was closed as wontfix because it would almost certainly introduce backwards-incompatible changes On a related now, you mentioned that none of the libraries you've mentioned are sufficiently polished. What further work do they need? As I see it, my main omission right now is documentation, though that is in progress. Regards, Andy On 27 May 2012 21:54, Iván Raskovsky <raskov...@gmail.com> wrote: > The generic class based views were introduced in 1.3, since then they > haven't seen much love. I feel the most wanted missing views are the > formsets related ones (specially the inline_formsets related ones). > > I've written to the list some months ago[0] with no reply. Luckily I'll > get more traction this time. Several projects have popped up[1, 2, 3] to > cover this area. Each one has different approaches. > > Ticket #16256[4] is tracking this changes > > * enhanced_cbv[0] * > > Tries to maintain a similar API to the existing views and the admin > inlines. Creates three generic views for a multiple formsets view, multiple > model_formsets view and a model with multiple inline_formset view. Joins > the update and create views in one view. > > * extra-views[1] * > > Keeps the current API as much as possible adding views for a one formset > and for one model_formset and adds views for working with > inline_formsets and generic inline_formsets. > > * cbv_utils[2] * > > I haven't played much with this one yet, but it only adds a view to work > with inline_formsets. It also proposes changes to the existing CVB APIs > to simplify adding this views[5]. > > Another related ticket is #10403[6]: a declarative syntax to define > FormSets so we don't need a special wrapper around the factories > simplifying creating inlines in a similar fashion as the admin's > InlineModelAdmin. > > So, we have 3 tested and working alternatives for these views. I think > none of them is polished enough as for inclusion to core. > > I have no idea how to move forward. Right now it seems kinda stalled. > Should we pick one implementation and start moving forward with that > one? If so, which one? Should we start a wiki page discussing the > different API decisions we need to make? > > I think we have the manpower to make this possible, the three > implementations shows people really need this in their projects and I'm > more than willing to spend time working on this. > > Any feedback will be greatly appreciated, > Iván > > [0] https://groups.google.com/d/msg/django-developers/aWRDIwDKDG8/gW3RGurxoZoJ > [1] https://github.com/rasca/django-enhanced-cbv > [2] https://github.com/AndrewIngram/django-extra-views/ > [3] https://github.com/tswicegood/cbv_utils > [4] https://code.djangoproject.com/ticket/16256 > [5] https://code.djangoproject.com/ticket/17557 > [6] https://code.djangoproject.com/ticket/10403 > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > 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. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. 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.
