Dear Joe, While I believe it is important to keep our discussions here professional, civil, and focused, it is also clear that your comment was an oversight and I agree with the feeling being expressed. That section of the book should be improved and expanded.
I trust nobody felt offended and I for sure was not. :-) Massimo On Friday, 6 December 2013 11:45:48 UTC-6, JoeCodeswell wrote: > > Dear Niphlod and Community, > > First, thanks Niphlod for putting me onto bootstrap > 2.3.2<http://getbootstrap.com/2.3.2/index.html>. > This looks GREAT. > > Finally, *I apologize* for using, what sometimes i *mistakenly think of *as > a technical term "SUCKS", in my above Post: > > // original from book SUCKS > > in my comments meant only for myself. This has *no place in this Very > Supportive Community*. > > > *I apologize.* > > Love and peace, > > Joe > > > On Friday, December 6, 2013 8:05:08 AM UTC-8, JoeCodeswell wrote: >> >> Dear Niphlod, >> >> Thanks for the response. I DID get something going by FireBugging my >> page. Here is what I came up with: >> >> >> <style> >> >> /* >> // original from book SUCKS >> body { background: url('images/background.png') repeat-x #3A3A3A; } >> a { color: #349C01; } >> .header h1 { color: #349C01; } >> .header h2 { color: white; font-style: italic; font-size: 14px;} >> .statusbar { background: #333333; border-bottom: 5px #349C01 solid; } >> .statusbar a { color: white; } >> .footer { border-top: 5px #349C01 solid; } >> // /original from book SUCKS >> */ >> // joe1 >> // WAS match [.header h1; .statusbar; .footer; ] = #XXXXXX == darkred = >> #880000 >> // WAS match [.header h1; .statusbar; .footer; ] = #XXXXXX =! darkred = >> #AA0000 >> // WAS #AA0000 = #BB0000 [too light for white links in menu ] >> // NOW #BB0000 = #AA0000 >> >> >> body { background: url('images/background.png') repeat-x #3A3A3A; } >> a { color: #349C01; } >> >> //.navbar {background: #AA0000; } >> .navbar-inverse .navbar-inner {background: #AA0000; } >> >> /* http://127.0.0.1:8000/songfest/static/css/bootstrap.min.css */ >> .navbar-inverse .nav > li > a{ >> color: #FFFFFF; >> /*color: #333333;*/ >> } >> >> div.flash { >> background-color: #AA0000; >> background-image: -moz-linear-gradient(90deg, #AA0000, #AA0000); >> } >> >> .page-header h1 { color: #AA0000; } //.header h1 { color: #AA0000; } >> .header h2 { color: white; font-style: italic; font-size: 14px;} >> .statusbar { background: #AA0000; border-bottom: 5px #349C01 solid; } >> .statusbar a { color: white; } >> .footer { border-top: 5px #AA0000 solid; } >> // /joe1 >> </style> >> >> The navbar is red & the links in the menu start out white. It could still >> use a little work on the menu hover. >> >> Thanks again for the response, Niphlod. I subbmitted a "book bug" == Issue >> 1802 <http://code.google.com/p/web2py/issues/detail?id=1802> >> >> Love and peace, >> >> Joe >> >> >> On Thursday, December 5, 2013 12:33:17 PM UTC-8, Niphlod wrote: >>> >>> I guess that piece of the book needs an update. >>> There is no .header nor .statusbar in the current scaffolding app. >>> >>> However, given that is based on bootstrap 2.3.2, you can find a boatload >>> of pointers in google on how to customize the color scheme . >>> >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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.
