#14802: feature request: ability to override default hidden_widget used to
render a
custom model field when marked as readonly in the admin
---------------------------------------------+------------------------------
Reporter: nickname123 | Owner: nobody
Status: reopened | Milestone:
Component: django.contrib.admin | Version: 1.2
Resolution: | Keywords: sprintdec2010
hidden_widget
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by cogat):
* milestone: 1.3 =>
Comment:
Just to clarify, a widget in Django is its representation of an HTML input
element, so it doesn't make sense to use it for anything that doesn't
involve displaying and handling an input element. So for read-only fields
there's no need to use a widget.
Given this, I think you're asking for each Field to have a method that is
called by admin that renders the field as a read-only HTML. That's
something I could get behind (it's better to attach field display to
fields than to models, and there are currently silly special-cases for
rendering BooleanFields as icons in the current code) but it needs a
design decision. Particularly, would the same method, or a variation on
it, be used to render the field in admin list views? What about mechanisms
for requiring external javascript/css files needed by the rendering? What
about specifying read-only fields (so the same method can be used) in non-
admin forms?
However, without a patch this won't make it into 1.3, so I'll remove the
milestone.
--
Ticket URL: <http://code.djangoproject.com/ticket/14802#comment:3>
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-upda...@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.
