#15667: Implement template-based widget rendering
---------------------------------------+--------------------------
Reporter: brutasse | Owner: brutasse
Type: New feature | Status: new
Milestone: 1.4 | Component: Forms
Version: | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
---------------------------------------+--------------------------
Comment (by brutasse):
Ok, so according to the chat we had on IRC with Carl an Jannis,
format_output and renderer / get_renderer should be deprecated since it's
too hard to keep them along with the new API and they're not considered
public. This is done in the latest version of the patch:
https://github.com/brutasse/django/compare/15667-template-widgets
If a MultiWidget defines a format_output() method, calling render() raises
a DeprecationWarning and uses template-based rendering anyway. Same with
the renderers:
* providing renderer as a kwarg during RadioSelect instanciation raises
DeprecationWarning
* the RadioSelect class doesn't have a renderer attribute anymore
* any call to get_renderer() raises a DeprecationWarning and returns
RadioFieldRenderer
* RadioSelect's render() will **always** use templates
The admin's RelatedFieldWidgetWrapper now has its template attribute and
get_context method.
The template loader still needs to be worked on (Carl's comment 15 above).
I'll give it a go tomorrow night, CEST.
--
Ticket URL: <http://code.djangoproject.com/ticket/15667#comment:19>
Django <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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
