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
perhaps it's time I dropped the css I've adopted from web2py! :)
On May 4, 6:04 pm, Thadeus Burgess wrote:
> I do not understand. I do not have any web2py css files.
>
> --
> Thadeus
>
>
>
> On Tue, May 4, 2010 at 11:58 AM, Carl wrote:
> > thanks for responding.
>
> > how do you deal with Web2py
I do not understand. I do not have any web2py css files.
--
Thadeus
On Tue, May 4, 2010 at 11:58 AM, Carl 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 Clev
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 wrote:
> I use clevercss for large projects, which is similar to SAS
4 matches
Mail list logo
