On Sat, 2007-04-21 at 23:55 -0700, ~Kender wrote:
> Along this same line, there's another issue with the RadioSelect
> widget.. It makes use of a rendering (returned by the render method)
> but the class is hardcoded in the method, so there's no way to supply
> an alternative renderer except to su
Along this same line, there's another issue with the RadioSelect
widget.. It makes use of a rendering (returned by the render method)
but the class is hardcoded in the method, so there's no way to supply
an alternative renderer except to subclass both classes (the renderer,
and the RadioSelect wid
Hi there,
I have a question regarding, shall I say, policy regarding where
attributes are placed on widgets (and MultiWidgets) that are rendered
as more than one HTML input.
Should what's passed in attrs be put on the individual inputs, or on
one encapsulating element (such as a div or an ul).
