#16922: Add a template-based form rendering system
--------------------------------+------------------------------------
     Reporter:  carljm          |                    Owner:  nobody
         Type:  New feature     |                   Status:  new
    Component:  Forms           |                  Version:  master
     Severity:  Normal          |               Resolution:
     Keywords:  form-rendering  |             Triage Stage:  Accepted
    Has patch:  1               |      Needs documentation:  0
  Needs tests:  0               |  Patch needs improvement:  1
Easy pickings:  0               |                    UI/UX:  0
--------------------------------+------------------------------------

Comment (by carljm):

 Hi Tim, a few thoughts:

 1. The code that was in that GSoC branch was eventually merged into
 [https://github.com/gregmuellegger/django-floppyforms django-floppyforms]
 and has seen updates there since, so I think it would be best to approach
 this in terms of a new Django branch copying/merging the desired code from
 floppyforms.

 2. I think that #15667 (rendering widgets via templates) alone addresses
 90+% of the issues people have with customizing markup in Django forms. I
 think that ticket is much higher priority than this one, presuming the
 performance issues can be addressed, or the performance cost is deemed
 acceptable.

 3. Once we have #15667, there are two additional steps that could be taken
 to resolve this ticket: either a) a straightforward port of the existing
 `.as_ul()` and `.as_p()` methods to render via an overridable template
 instead of by constructing HTML in Python, or b) a full integration of the
 extensively customizable form-layouts system that Gregor built for GSoC.
 To be honest, I am not sure the latter needs to be in Django, I think it
 works just fine as a third-party add-on (at least until/unless that third-
 party add-on proves itself as a de facto necessity a la South, which I
 don't think it has done yet). So I would be in favor of limiting the scope
 of this ticket to (a), and only even worrying about that once #15667 is
 fixed.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16922#comment:3>
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/064.59951d0fd78125936f876c619de55bb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to