On 05/15/2016 11:01 PM, Curtis Maloney wrote: > So this seems to leave us only part way to removing rendering decisions > from the form code -- your widgets can be templated, but your form code > still needs to decide which widgets...
Yep, one step at a time. With django-floppyforms templated widgets I've used a template filter that allows switching a widget's template path in the template that's rendering the form, placing more control into templates. I think integrating something like that could make sense as a next step. (Since widgets are Python classes that control not only markup generation but also data retrieval, control over widgets themselves needs to remain in Python code. But the rendering template could be given the option to customize the template used to render the widget.) Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5739564A.6010207%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
