On 10 October 2011 13:13, Russell Keith-Magee <russ...@keith-magee.com>wrote: > > The approach taken by django-messages should be the model here. When a > new messages framework was proposed for Django in 1.2, an effort was > made to find out all the features that were desirable, and then pull > together all those features into a third party library that borrowed > code from all the available implementations. The same approach should > be taken here -- find out all the features that we want to have in > generic views (e.g., formsets, fieldsets, filtering, ordering, table > rendering), build an amalgam library that takes the best parts from > all the available 3rd party libraries, and develop that into a single > patch that can be applied to trunk. >
On this point, I'd like to draw attention to my own set of class-based views which provide formsets functionality, mimicking the APIs of the existing CBVs as closely as possible. The ultimate goal was to attempt to reimplement some of Django's admin as a proof-of-concept. It doesn't support any higher-level functionality like fieldsets, filtering and sorting, and there's an issue with pagination (see this ticket: https://code.djangoproject.com/ticket/16432), but it's fairly feature-complete and could be a good starting point. - Andrew -- 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.
