Michael Elsdörfer wrote:
> Why stop at widgets?
Basically, because I was struggling with widgets many times but didn't
have any practical needs for changing a label, for example. I don't say
it's useless or something but I just can't defend it from my experience.
> By the way, IIRC the following should already somewhat do what you
> want in most cases, although it's obviously not very nice:
>
> class ArticleForm(ModelForm):
> author =
> Article._meta.get_field('author').formfield(**custom_options)
> class Meta:
> model = Article
I do something like this right now. I even have a shortcut function
"model_field" for this which makes it shorter. However, see:
class ArticleForm(ModelForm):
author = model_field(Article, 'author', attrs)
class Meta:
model = Article
every such field definition forces me to repeat field's name twice and
also repeat a model that is already set in Meta.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
