On Fri, Sep 20, 2013 at 2:41 PM, Marc Tamlyn <[email protected]> wrote:
> This is partly because there's no obvious correct implementation of them ;) > > Yes, I think these views should exist. But they go with the same body of > work as handling multiple forms, inline formsets etc. At present I have no > yet found the time to think about this problem, as a whole and come up with > a single consistent solution. > I'm not sure FormSetView *should* exist. I'd be a lot more inclined to look at something like FormContainer -- a form-like container that can contain multiple forms and formsets. There's a sample implementation on #18830 in the context of extending FormWizard to support combinations of form and formset. https://code.djangoproject.com/ticket/18830 If you had a form container, you wouldn't need a new generic view -- you can just use FormView, and use the FormContainer as the form. (I'd also like to rethink generics in general, but that's a whole other conversation… and one that I need to internally progress from vauge rambling to slightly coherent proposal… and then find time to work on :-) Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
