Using a library from contrib sounds like a good approach and I wish this was done before adding bootstrap. Perhaps it should be done now, for all future formstyles?
Even now, bootstrap is really just covering bootstrap-horizontal (there are other form options within BS). Regards, Ales On Tuesday, August 20, 2013 11:15:50 PM UTC+2, Anthony wrote: > > On Tuesday, August 20, 2013 2:01:54 PM UTC-7, Paolo Caruccio wrote: > >> Anthony you are right about the scaffolding, But currently, web2py >> renders forms with formstyle="bootstrap" which have css classes not used >> anymore in bs3. >> > > This doesn't mean the scaffolding app has to remain on Bootstrap 2 > forever. I'm not sure we should have created a formstyle called "boostrap", > though. Instead, we should probably put a formstyle.py in contrib that > includes several custom formstyles, including ones for Bootstrap 2 and > Bootstrap 3. Then you would do: > > from gluon.contrib.formstyle import bootstrap3 > form = SQLFORM(..., formstyle=bootstrap3) > > In any case, the current "bootstrap" formstyle can continue to work with > Bootstrap 2, and in that sense, it won't break backward compatibility. That > doesn't mean the scaffolding app can't change to Bootstrap 3. > > Anthony > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
