On Mon, Jun 6, 2011 at 7:49 PM, Chris Beaven <[email protected]> wrote:
>
> I'd say it would be more backwards compatible, and still reasonably concise
> to just have a separate attribute:
>
> disabled_choices = ('bananas',)
>
OK. I was trying to avoid adding attributes to the widget, but it's
definitely backwards compatible.
I've attached a patch to ticket 16149:
https://code.djangoproject.com/attachment/ticket/16149/select_with_disabled.diff
Do people generally agree with this approach? I will continue work if so.
Still todo: adding similar functionality to other widgets where it makes
sense and adding tests. I could also add disabled_choices support to
forms.Choicefield, similarly to the way choices is handled now. Let me know
if you think this is useful.
Thanks,
Jody
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
