I was a bit torn in views here, but I see your point. It appears as
quite a different element, similarly if you were to create an auto
complete widget (combo-box style) I wouldn't expect that to be an
option of widgets.SelectTextBox. The way I see it widgets are not a way
to create (x)html tags but abstracted elements that are generally more
like GUI programming like than html
Jorge Godoy wrote:
> Jared Kuolt <[EMAIL PROTECTED]> writes:
>
> > Where do you draw the line when supporting attributes? We could
> > support all given attributes for each element, but I think that lends
> > itself to being an incredible headache.
> >
> > You can currently do this with attrs:
> >
> > widgets.SelectField(options=options_b,
> > attrs={"multiple":"True", "size":"10"},
> > name="Multiple",
> > default=["val3","val4"])
>
> Don't you think it is so much difference from one to the other that it is
> worth it? What other element presents that kind of different behaviour?
> Maybe "textarea" with one row when compared to another with "n" rows, but it
> is very uncommon to use a textarea with just one row.
>
> It is doable with the attrs attribute so it is not all that urgent, but it
> would be more intuitive to have a widgets.ListboxField() with the extra
> attribute, IMHO.
>
>
>
> --
> Jorge Godoy <[EMAIL PROTECTED]>
