#6632: FormSet, ModelFormSet, InlineFormSet and inlines for newforms in trunk
-----------------------------------------------------+----------------------
Reporter: Petr Marhoun <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component:
django.newforms
Version: SVN | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------------------------+----------------------
Comment (by Petr Marhoun <[EMAIL PROTECTED]>):
* Patch is based on the new patch from #6631 and depends on it.
* Some bugs in inlines are fixed so inlines really works as part of a
form now.
* Caching of querysets in inner form is solved - but the solution is ugly
and has to be improved (I will think about it).
* Bug from the previous comment fixed (thanks).
* Option fieldset_html_output_method is removed because it is to complex
and could be replaced be !BaseForm._inline_html_output.
* Some options are renamed to be shorter.
* Complete list of options - form, base_form, deletable, is_empty_fields,
is_empty_exclude, fieldset_attrs, fieldset_legend, num_extra, orderable,
output_type (and all from inner form). (I am sure that native speakers
could find better names.)
--
Ticket URL: <http://code.djangoproject.com/ticket/6632#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
