Are you talking about the stuff at the top of web2py.css marked "these MUST stay" ( http://code.google.com/p/web2py/source/browse/applications/welcome/static/css/web2py.css#1)? Now that we're using Bootstrap, I think most if not all of that section can probably be cut since Bootstrap already handles basic styles. web2py.css should be limited to web2py-specific things only.
Anthony On Monday, August 20, 2012 9:13:12 PM UTC-4, Michael W wrote: > > By default web2py.css is pretty heavy-handed on form controls. Would it > be possible to restrict the form controls in web2py.css by class? It might > require setting a default class on all generated forms. grid and smartgrid > do this already, but using default SQLFORM() does not set a default class > on the form currently. My thought is to change SQLFORM so it sets a > default 'web2py_form' class which is what grid and smartgrid already do. I > would then restrict all the form controls in web2py.css to this class. > This would make it much easier to use non-web2py css frameworks like > bootstrap with forms. Right now to get it working properly I have to > comment/remove a lot from web2py.css to get it using bootstrap fully in my > forms, even with the new bootstrap formstyle that's in trunk. > > Would this break anything? > > Michael > --
