optional arg. 'description' for widget?

On 12/30/06, Alex Koval <alex.v.kovalgmail.com> wrote:
> I found that pretty often I need a
"description" being passed to field to
> display. I already subclassed
> a few widgets to get 'description' argument, and
display it where needed.
> For example here is
> modified TextInput widget:
> http://dpaste.com/4207/
>
> But I feel that the copy/paste I do with code here is
wrong. Its much easier
> to have this optionally
> available inside of django.newforms by default, so if
description is passed,
> it will be printed.
> Yes, 90% of fields do not need description, but
sometimes it is needed.

Hi Alex,

I'd rather avoid feature creep with the newforms library,
and I'd
consider a "description" to be part of the
presentation of a form
rather than part of the content of a form. So I don't think
we'll add
a "description" option for the time being. Of
course, there's nothing
stopping you from implementing it in your own Widget
subclasses, as
you've already done.

BTW, future questions/proposals like this should go to the
django-developers mailing list -- that's where we talk about
changes
and improvements to Django itself.

Adrian

-- 
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 31/12/06, Adrian Holovaty <holovatygmail.com> wrote:
>
> On 12/30/06, Alex Koval <alex.v.kovalgmail.com> wrote:
> > I found that pretty often I need a
"description" being passed to field to
> > display. I already subclassed
> > a few widgets to get 'description' argument, and
display it where needed.
> > For example here is
> > modified TextInput widget:
> > http://dpaste.com/4207/
> >
> > But I feel that the copy/paste I do with code here
is wrong. Its much easier
> > to have this optionally
> > available inside of django.newforms by default, so
if description is passed,
> > it will be printed.
> > Yes, 90% of fields do not need description, but
sometimes it is needed.
>
> Hi Alex,
>
> I'd rather avoid feature creep with the newforms
library, and I'd
> consider a "description" to be part of the
presentation of a form
> rather than part of the content of a form. So I don't
think we'll add
> a "description" option for the time being. Of
course, there's nothing
> stopping you from implementing it in your own Widget
subclasses, as
> you've already done.
>
> BTW, future questions/proposals like this should go to
the
> django-developers mailing list -- that's where we talk
about changes
> and improvements to Django itself.
>
> Adrian
>
> --
> Adrian Holovaty
> holovaty.com | djangoproject.com
>

Hi Adrian,

Django model fields already have the help_text parameter
that is
displayed in the admin app and it not easily available to
template
designers without writing a custom template tag to extract
it. I think
it would be very useful if the newforms fields had the
ability to
display the help_text without having to resort to writing a
custom
tag.

regards

matthew

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---