Man, I'm such a clairvoyant!! This was already brought up to @massimo in the past. I'd go with a new formstyle='bootstrap3' to handle all changes. It's unthinkable to have it otherwise and maintain all things working bs2-->bs3 without heavy FOUC. Don't loose your mind over it ^_^
On Tuesday, August 20, 2013 11:01:54 PM UTC+2, 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. Therefore we should use jquery to adapt the rendered html but we could > see heavy flash of unstyled content phenomenon. Another way is to use the > server DOM manipulation in the controller or in the view or lastly modify > the web2py code but the latter way infringes the backward compatibility if > someone want build application working also on unsupported browsers by > using bs2. I'm testing bs3 since rc1 on web2py and this is my conclusion > but I could be wrong. > > -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
