#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 jezdez):
I agree with !AndrewIngram's plan for staying close to the already
existing form related mixins and I believe rasca's approach is basically
trying to do the impossible (porting admin) to early in the API design.
So let's step back a bit and first implement the formset related views and
then see what glue code or concept is needed to help concrete
implementations like the admin to use the new API. We shouldn't carry
around potentially bad API decisions in the admin into the generic views
just to get it done quicker.
--
Ticket URL: <https://code.djangoproject.com/ticket/16256#comment:15>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
