I also didn't notice any changes between Bootstrap 2.2.2 and 2.3.1 as far as web2py integration goes. Probably a good time to drop the update into dev. I didn't test the newer jQuery, 1.9.x.
When upcoming Bootstrap 3 and jQuery 2 come, it won't be so simple. A shortlist of somewhat disruptive developments: - Bootstrap 3 will be mobile-first (responsive css file isn't separate anymore) - Bootstrap 3 will drop the IE 7 support - jQuery 2 will drop the support for IE 6, 7 and 8. That's something to keep in mind for the future... List of changes is a lot longer, of course (some of them quite nice): https://github.com/twitter/bootstrap/pull/6342 http://blog.jquery.com/2013/04/09/jquery-2-0-beta-3-released/ This quote from older jQuery blog post might calm things down a bit: We fully expect that most Internet web sites may continue to use jQuery 1.x > for quite a while, as long as older versions of IE still comprise a large > proportion of web surfers. And so the jQuery team will also continue to > support both the jQuery 1.x and 2.x lines. Don’t feel like you’re missing > something or falling behind by using 1.9 on your web site, since the APIs > for 1.9 and 2.0 are the same. On the other hand, from the Bootstrap 2.3.1 release blog post: Aside from the fixes in this release, future bugs will only be addressed in > 3.0, or punted entirely, as appropriate. Regards, Ales On Sunday, April 14, 2013 5:36:40 PM UTC+2, Paolo Caruccio wrote: > > I found the problem causing the submenu display failure. Twitter bootstrap > shows the submenu with the "click". In web2py, instead we use the "hover". > Since bootstrap has implemented a js function that sets the height of the > navbar, having the collapsed state, on click event we have to override it. > I added a function that adjusts the height of the navbar on hover event. > Unfortunately there is a small initial spring effect, but I think that it > is acceptable. > I will send a patch in the next few minutes. > > Regarding the size of the small button you can increase it by simple css > rules. For example: > > . navbar. btn-navbar. icon-bar { > width: 36px; > height: 4px; > } > . btn-navbar. icon-bar +. icon-bar { > margin-top: 6px; > } > > to be added to the section "Overriding Bootstrap.css Rules" in > web2py_bootstrap.css. But I think it's a question of taste so it is in my > opinion that it is preferable to leave the default values in the > distributed version of web2py. > > Finally, I noticed that in web2py we have an old version of jquery (1.8.3 > vs 1.9.1) and an old version of bootstrap (2.2.2 vs 31.2). I'm pretty sure > that updating these technologies does not lead to side effects. > > > Il giorno domenica 14 aprile 2013 16:52:03 UTC+2, Massimo Di Pierro ha > scritto: >> >> Can we increase width that triggers the first behavior (small button)? >> >> On Sunday, 14 April 2013 05:06:01 UTC-5, Paolo Caruccio wrote: >>> >>> The first behavior (a small button is shown on narrow screen) is normal. >>> The second no. Original behavior was to show all submenu when you clicked >>> on small button. You could check this on web2py 2.3.0. Something broke this >>> I'll investigate and submit a patch asap. >>> >>> Il giorno sabato 13 aprile 2013 23:29:39 UTC+2, Massimo Di Pierro ha >>> scritto: >>>> >>>> In twitter bootstrap and web2py when the screen is too narrow the menu >>>> display as a single button which triggers a drop down. This happens to me >>>> every time I give a talk and the menu disappears because the screen gets >>>> narrower on a projector. Moreover when the menu is a dropdown, submenus do >>>> not work? >>>> >>>> Any suggestions for changing this behavior? >>>> >>>> Massimo >>>> >>> -- --- 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.
