We have extra JS to make the menu names clickable (bootstrap does not support that). we have extra classes to hangle web2py specific classes, for example the ones for the grid. Nothing else I can think of.
On Friday, 16 November 2012 23:59:50 UTC-6, Rod Watkins wrote: > > Hello everyone, > > I am in the process of preparing my web app to switch over to bootstrap. I > wanted to get a better understanding of how the web2py implementation > departs in any way from the standard vanilla bootstrap library. > > I already understand that the welcome scaffold app makes use of some > unique js to make the menu act differently than the standard bootstrap > navbar (mouse over rather than clicking). But I also noticed that the > web2py scaffold app does not rely on the viewport size (media queries) to > switch over to the mobile style menu--relying instead on the user agent as > reported by web2py. Other than those two, do all the other standard > bootstrap features just work out of the box, so to speak? > > A related question: if one wished to forgo the web2py departures > (especially with regard to the responsive part of bootstrap) to have a > plain vanilla bootstrap experience, are there any gotchas I should expect > when using, for example, the formstyle='bootstrap' setting for forms? > > I'd like to get other's experiences before I begin the transition. > > Thanks everyone!! > > Rod > --
