On 3/8/06, limodou <[EMAIL PROTECTED]> wrote: [...] > Because formfield doesn't has a verbose_name property. So I want to > ask why there is no verbose_name in FormField __init__() function. I > think if there is verbose_name, so create a form code will be easier.
I would also be interested in the answer to this. Is it just waiting for a patch or is it a deep design decision to keep form fields for input only to force everything else into custom tags (which is how admin seems to do it)? I would have thought that DRY would mean that FormField should have some sort of labelname property otherwise have to repeat the label text in every different form template file. Ticket http://code.djangoproject.com/ticket/1191 is vaguely related to this -- Phil Davis --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
