#25702: Port ModelAdmin.fieldset to BaseForm -------------------------------------+------------------------------------- Reporter: Psycojoker | Owner: nobody Type: New feature | Status: closed Component: Forms | Version: master Severity: Normal | Resolution: duplicate Keywords: form modeladmin | Triage Stage: layout admininterface | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by charettes):
* status: new => closed * resolution: => duplicate Comment: This looks like a duplicate of #6630. I have to say I agree with Carl that formsets are too much display logic in Python. They make a bit more sense at the admin level since you want a quick an dirty way to order your fields without having to write a template. In the case of forms efforts have been made to move the whole logic to the template level and eventually deprecate the `as_(p|table|ul)` methods which are the only methods that would rely on this option. If you disagree with these ticket resolutions please voice your opinion on the developer mailing list. In the meanwhile I'll just mark this ticket as a duplicate. -- Ticket URL: <https://code.djangoproject.com/ticket/25702#comment:2> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.a2c23ec0e63eb257cd31fdc04d6327b9%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.