ok. I applied the V2. Massimo
On Monday, 18 June 2012 16:41:34 UTC-5, Paolo Caruccio wrote: > > Massimo, > > "bootswatch.css" overwrites some css rules of "bootstrap.min.css" and > "web2py.css" to allow layout to comply with bootstrap twitter theme (and > consequently with bootswatch themes derived from it). > > "bootswatch.css" is a web2py file like "web2py.css", therefore we can edit > it. Maybe we should change its name in "bootswatch4w2p.css" to remove any > doubt. > Having two file "bootswatch.css" and "web2py.css" is useful: if someone > doesn't like bootstrap and he want apply its own theme, he has only to > remove "bootstrap.min.css" and "bootswatch.css" to obtain basic web2py css > theme > > Instead "bootstrap.min.css" (twitter and bootswatch have the same name) > contains the original bootstrap css theme (from twitter site) or modified > one (from bootswatch site). > > > Il giorno lunedì 18 giugno 2012 21:06:20 UTC+2, Massimo Di Pierro ha > scritto: >> >> How is that possible? You edited bootswatch.css? >> >> On Monday, 18 June 2012 05:24:36 UTC-5, Paolo Caruccio wrote: >>> >>> Massimo, >>> >>> actually files with prefix V2_ allow this: download and apply in w2p a >>> bootswacth theme without other actions by user. >>> >>> >>> Il giorno lunedì 18 giugno 2012 06:39:23 UTC+2, Massimo Di Pierro ha >>> scritto: >>>> >>>> I included your patch but not version V2. That is because we do not >>>> want to mantain our own modified bootswatch. People should be able to >>>> download a theme and use it without editing. Can this be addressed in >>>> web2py.css? >>>> >>>> On Sunday, 17 June 2012 18:42:12 UTC-5, LightDot wrote: >>>>> >>>>> I have tested the V2 versions attached with Issue 856 and they seem to >>>>> address the issues perfectly. >>>>> >>>>> Regards >>>>> >>>>> On Sunday, June 17, 2012 9:14:33 PM UTC+2, Paolo Caruccio wrote: >>>>>> >>>>>> Patch submitted http://code.google.com/p/web2py/issues/detail?id=856 >>>>>> >>>>>> Il giorno domenica 17 giugno 2012 17:32:53 UTC+2, Massimo Di Pierro >>>>>> ha scritto: >>>>>>> >>>>>>> Can you coordinate with Andrew and Paolo and send me a single fix >>>>>>> that applies to latest trunk and addresses the outstanding issues? >>>>>>> >>>>>>> On Sunday, 17 June 2012 08:42:50 UTC-5, LightDot wrote: >>>>>>>> >>>>>>>> I have tried your updated bootswatch.css from another thread here, >>>>>>>> which also incorporates this fix. I confirm that BS 2.0.4 works now. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> On Sunday, June 17, 2012 12:33:52 AM UTC+2, Paolo Caruccio wrote: >>>>>>>>> >>>>>>>>> LightDot, >>>>>>>>> >>>>>>>>> try to append in static/css/bootswatch.css this rule: >>>>>>>>> >>>>>>>>> .dropdown-menu ul{display:block;} >>>>>>>>> >>>>>>>>> I spotted the issue some days ago, but I didn't propose a patch >>>>>>>>> because web2py still has bs 2.0.2 >>>>>>>>> >>>>>>>>> Let me know if the fix works for you also. >>>>>>>>> >>>>>>>>> Il giorno domenica 17 giugno 2012 00:27:18 UTC+2, LightDot ha >>>>>>>>> scritto: >>>>>>>>>> >>>>>>>>>> Changes in dev in the last week or so have effect on Bootstrap. >>>>>>>>>> 2nd level submenus don't work anymore if using Bootstrap 2.0.4, >>>>>>>>>> while >>>>>>>>>> bundled 2.0.2 works. >>>>>>>>>> >>>>>>>>>> - clean welcome app from latest dev, Bootstrap css and js >>>>>>>>>> upgraded to 2.0.4 >>>>>>>>>> - clicking over the yellow "web2py" opens the first submenu level >>>>>>>>>> - clicking or hovering over e.g. Documentation, does nothing. >>>>>>>>>> >>>>>>>>>> Tested in Firefox 13 and Opera 12... Are there plans to update >>>>>>>>>> Bootstrap to 2.0.4 in web2py itself? >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, June 15, 2012 4:49:29 PM UTC+2, Paolo Caruccio wrote: >>>>>>>>>>> >>>>>>>>>>> Andrew, do you mean the code for old auth_navbar style? If yes, >>>>>>>>>>> I think it's better if you open a new thread for asking to the >>>>>>>>>>> web2py users >>>>>>>>>>> what style they prefer and after we will send a patch to Massimo. >>>>>>>>>>> It's >>>>>>>>>>> possible that most of w2p users loves the current style (bootstrap >>>>>>>>>>> buttons >>>>>>>>>>> group). >>>>>>>>>>> >>>>>>>>>>> Il giorno giovedì 14 giugno 2012 22:55:38 UTC+2, Andrew ha >>>>>>>>>>> scritto: >>>>>>>>>>>> >>>>>>>>>>>> Hi Paolo, >>>>>>>>>>>> >>>>>>>>>>>> Are you able to send a patch to Massimo for your layout and >>>>>>>>>>>> bootswatch files. The bootstrap menu issue is holdnig up 2.0 and >>>>>>>>>>>> I think >>>>>>>>>>>> your changes have addressed this. Would love to see it in trunk. >>>>>>>>>>>> >>>>>>>>>>>> If you can't I can have a go at working out what you did. >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> >>>>>>>>>>>> Andrew W >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thursday, June 7, 2012 8:24:44 PM UTC+12, Paolo Caruccio >>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> I'm afraid you can not do it. The first item in the dropdown >>>>>>>>>>>>> menu (having class="dropdown") can not contain an URL. The >>>>>>>>>>>>> structure of the >>>>>>>>>>>>> dropdown menu is as follows (taken from this page >>>>>>>>>>>>> http://twitter.github.com/bootstrap/components.html#navbar): >>>>>>>>>>>>> >>>>>>>>>>>>> Adding dropdown menus >>>>>>>>>>>>> >>>>>>>>>>>>> Adding dropdowns and dropups to the nav is super simple, but >>>>>>>>>>>>> does require the use of our javascript >>>>>>>>>>>>> plugin<http://twitter.github.com/bootstrap/javascript.html#dropdowns> >>>>>>>>>>>>> . >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 1. <ul class="nav"> >>>>>>>>>>>>> 2. <li class="dropdown"> >>>>>>>>>>>>> 3. <a href="#" >>>>>>>>>>>>> 4. class="dropdown-toggle" >>>>>>>>>>>>> 5. data-toggle="dropdown"> >>>>>>>>>>>>> 6. Account >>>>>>>>>>>>> 7. <b class="caret"></b> >>>>>>>>>>>>> 8. </a> >>>>>>>>>>>>> 9. <ul class="dropdown-menu"> >>>>>>>>>>>>> 10. ... >>>>>>>>>>>>> 11. </ul> >>>>>>>>>>>>> 12. </li> >>>>>>>>>>>>> 13. </ul> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Il giorno giovedì 7 giugno 2012 04:13:19 UTC+2, LightDot ha >>>>>>>>>>>>> scritto: >>>>>>>>>>>>>> >>>>>>>>>>>>>> I can confirm this, using fresh welcome application and >>>>>>>>>>>>>> Bootstrap upgraded to 2.0.4. >>>>>>>>>>>>>> >>>>>>>>>>>>>> If a menu item has both an URL specified and also additional >>>>>>>>>>>>>> submenus, these don't get displayed. Regardless if this is a >>>>>>>>>>>>>> first or a >>>>>>>>>>>>>> second level menu item. If the URL is set as None, additional >>>>>>>>>>>>>> submenus >>>>>>>>>>>>>> display properly. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wednesday, June 6, 2012 11:13:48 PM UTC+2, Paolo Caruccio >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Szimszon, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> is it a new application or have you replaced an old layout >>>>>>>>>>>>>>> with that new one? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Il giorno mercoledì 6 giugno 2012 13:42:22 UTC+2, szimszon >>>>>>>>>>>>>>> ha scritto: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have issue with dropdown menu when the main menu is a >>>>>>>>>>>>>>>> link too. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If I click on the main menu than that menu is activated and >>>>>>>>>>>>>>>> I can't access the items below it with any means :( >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Il giorno mercoledì 6 giugno 2012 13:42:22 UTC+2, szimszon >>>>>>>>>>>>>>> ha scritto: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have issue with dropdown menu when the main menu is a >>>>>>>>>>>>>>>> link too. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If I click on the main menu than that menu is activated and >>>>>>>>>>>>>>>> I can't access the items below it with any means :( >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>
