[patch] Support for nested/compound forms for newforms

[Jeroen van Dongen <jeroen at jkwadraat.net>]

The attached file contains a few classes to provide the ability to nest forms in forms.
See also ​http://groups.google.com/group/django-developers/t/b39ec8990e756b53.

[Jeroen van Dongen <jeroen at jkwadraat.net>]

In the current state it's useable except for the FormList functionality. There's something wrong with it (see Known bugs in the attached file), but I've currently no time to hunt it down, has to wait 'till later this week.

[Gary Wilson <gary.wilson@…>]

Have you looked at the FormSet code recently added to django.newforms.formsets in the newforms-admin branch?

[Brian Rosner]

I am closing this ticket as support for this is already in newforms-admin in django.newforms.formsets.

[Joost Cassee]

As I see it this is not at all like the FormSet. The FormSet is about multiple forms *of the same type*, while superform.py allow compound or nested forms. See the doctest code.

I believe this functionality is not yet present in Django. Please reopen if I am correct.

[mccartney]

I confirm, form sets are something different.
I would vote for having the nested forms.

[sdolan]

Updated version to work w/1.2 (should work with all 1.0+).

[sdolan]

I updated this patch in response to a stack overflow question ​http://stackoverflow.com/questions/3114656/django-compound-nested-subforms. I removed the doctests, and added unittests (in my own "django-common" repository) that have ~90% coverage covering the different form combinations (ModelForms, multiple SubForms, and mixed Fields + SubForms). If this is something people are interested I can work up a patch that integrates the SubForm class into the Django core with accompanying unit tests/docs.

[twoolie]

I think that if people knew about this patch they would be VERY interrested. This could make complicated form creation far easier by removing the mix an math approach of putting a ton of tiny forms in a template and combining all the data manually in one's view.

[sdolan]

Removed a debug raise statement that slipped by.

[mnbayazit]

Added iter, getitem, and save()

[cato]

Still not reviewed.

[Russell Keith-Magee]

It wasn't reviewed because the fundamental idea was rejected. If you think the idea should be reconsidered, you need to start a discussion on Django-dev, not just reopen the ticket.

[Antti Kaihola]

Why not make a reusable app out of this patch and put it on ​PyPI and ​djangopackages.com? Wouldn't it make sense since the patch doesn't modify Django at all, just adds some classes.