On Wed, Oct 19, 2011 at 1:21 PM, Tom Evans <tevans...@googlemail.com> wrote: > I suggest you rethink your approach. Subclassing ForeignKey so that > you can build a better widget does not seem sane. Why do you think > this would help?
because the simplest way to make it reusable is to have "from myapp.fields MyCustomField" and use it as any other field. even if it's just to change default widget on ForeignKey. also, it's probably more realistic that i'll have access to model instance in field then in widget. Aljosa -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
