#6735: Class-based generic views
------------------------------------+---------------------------------------
Reporter: jkocherhans | Owner: telenieko
Status: assigned | Milestone: post-1.0
Component: Generic views | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by telenieko):
With 1.0 on the streen it's time to start with the killer features for 1.1
(yes I intend this one to go for 1.1 ehehe).
Question one: Would you love a ListEditView() which used FormSets to
edit/create multiple objects? (Just like an EditView but for more than one
form).
Question mostly for Jacob:
The documentation for the class based generic views
([http://tinyurl.com/django-6735-docspatch see current docs diff]) has to
document all the methods available for inheritance which makes the
document itself a bit cumbersome (lots of details that people wanting to
"just use" those views are not interested in). So, would it be reasonable
to do a topics/generic-views.txt with the introduction and the usage
details; And then put on ref/generic-views.txt the implementation details
and how can one inherit/develop generic views on top of the new ones?
--
Ticket URL: <http://code.djangoproject.com/ticket/6735#comment:23>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
