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.
Il giorno martedì 20 agosto 2013 22:34:50 UTC+2, Anthony ha scritto: > > On Tuesday, August 20, 2013 1:22:19 PM UTC-7, Paolo Caruccio wrote: > >> Unfortunately bs3 has dropped some components used by web2py, for example >> submenus, has changed many classes and so on. In other words it's a >> different framework that requires changes in web2py code which - currently- >> infringe the backward compatibility. Moreover IE7 and FF3.6 aren't >> supported anymore. Of course it's possible create customized html layouts >> based on bs3 but I don't think that web2py can apply for default this new >> framework. >> > > Backward compatibility does not apply to the scaffolding app (it has > changed many times in the past) -- when you upgrade, you don't have to > upgrade your app (the scaffolding is just a starting point). There is also > no hard requirement that the scaffolding layout/CSS must work on all > historical versions of IE and FF. Not saying we should switch immediately, > but these are not necessarily hard constraints. > > 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.
