Ah, perhaps :) You can always stick it in a w2p.css.
If you need to upgrade the w2p.css (which does not happen that often) it will be placed in the welcome app if you update from the repository. For appadmin, I usually have to copy new versions over manually. -- Thadeus On Tue, May 4, 2010 at 12:50 PM, Carl <[email protected]> wrote: > perhaps it's time I dropped the css I've adopted from web2py! :) > > On May 4, 6:04 pm, Thadeus Burgess <[email protected]> wrote: >> I do not understand. I do not have any web2py css files. >> >> -- >> Thadeus >> >> >> >> On Tue, May 4, 2010 at 11:58 AM, Carl <[email protected]> wrote: >> > thanks for responding. >> >> > how do you deal with Web2py upgrades: an upgrade that modifies its >> > css. Have you split from Web2py's css files, do you handle them >> > outside of CleverCSS or a third way? >> >> > On May 4, 5:27 pm, Thadeus Burgess <[email protected]> wrote: >> >> I use clevercss for large projects, which is similar to SASS. >> >> >> However, for dynamic css I use it as a template. And for small apps I >> >> just write css straight up in the static folder. >> >> >> -- >> >> Thadeus >> >> >> On Tue, May 4, 2010 at 9:12 AM, Carl <[email protected]> wrote: >> >> > hi, >> >> >> > Is anyone using SASS to manage their CSS definitions? >> >> >http://sass-lang.com/ >> >> >> > And if so, how have you managed web2py's css files? >> >> >> > thanks >
