#16256: More class based views: formsets derived generic views
---------------------------------------+-------------------------------
Reporter: rasca | Owner: rasca
Type: New feature | Status: new
Milestone: 1.4 | Component: Generic views
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 1 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+-------------------------------
Comment (by rasca):
Hi Andrew, my EnhancedFormSet et al resembles the admin's InlineAdmin,
where we can set some things needed to instantiate the formset. For
example, you've put {{{extra}}} and {{{can_order}}} inside the Mixin
class, but we need to have a different set of parameters for each formset,
so I made another class encapsulating this parameters.
I don't like the naming though.
About splitting everything in steps... I'm not sure about it. An
implementation of inlineformsets that doesn't allow more than one inline
doesn't make much sense IMO. I might bring this up in django-developers,
gonna try #django-dev first.
But surely, another ticket for multiple Forms or ModelForms would be
great! I think they will be fairly easy to build from what we have so far.
--
Ticket URL: <https://code.djangoproject.com/ticket/16256#comment:12>
Django <https://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.
