On Nov 21, 12:31 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> If you want custom behavior from the form, you should probably be
> writing a custom form class.
>
I don't think this is that custom of a behavior. The old forms had
this behavior by default and this customization doesn't affect
b
On Nov 21, 8:17 pm, Cristian <[EMAIL PROTECTED]> wrote:
> Thanks for the info. Unfortunately, I forgot to mention key point
> (absentminded me) that I'm using the form_for_model function to create
> many of these Form classes. Since I create many of these Form classes
> on the fly, is there anothe
On 11/21/07, Cristian <[EMAIL PROTECTED]> wrote:
> Thanks for the info. Unfortunately, I forgot to mention key point
> (absentminded me) that I'm using the form_for_model function to create
> many of these Form classes. Since I create many of these Form classes
> on the fly, is there another way o
Thanks for the info. Unfortunately, I forgot to mention key point
(absentminded me) that I'm using the form_for_model function to create
many of these Form classes. Since I create many of these Form classes
on the fly, is there another way of specifying input element
attributes?
Thanks
On Nov 20
On 11/21/07, Cristian <[EMAIL PROTECTED]> wrote:
> I've been using the old forms for a while but I'm starting to move
> over to the new forms module. One difference that's annoying me is the
> lack of the class attribute in the input tags. I use the class tags in
> my CSS to change colors and widt
Hi,
I've been using the old forms for a while but I'm starting to move
over to the new forms module. One difference that's annoying me is the
lack of the class attribute in the input tags. I use the class tags in
my CSS to change colors and widths. Is there a way to add those back
in (without hav
6 matches
Mail list logo
