On Fri, Jan 16, 2009 at 5:06 AM, Flavio Curella <flavio.cure...@gmail.com> wrote: > Wouldn't it be more granular to allow the overrides on the field name > basis? something like:
Hm, I think that's a separate issue: the goal of the patch is to easily make "mixins" providing custom widgets (etc.) easier. There's already a couple of easy ways to use a custom form field for a particular model field: you can extend ``formfield_for_dbfield`` and dispatch based on ``db_field.name``, or use a custom ModelForm. Of those, I'd use the second, btw. Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
