Before you get too far into it, you might want to take a look at CleverCSS. (http://sandbox.pocoo.org/clevercss/). Might be able to incorporate it to save some time.
On Jul 9, 5:06 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > On Jul 9, 2009, at 2:26 PM, Speedbird wrote: > > > > > I'd say Safari's caching, it is known that safari does not handle > > changes in certain type of files very well (a feature or a nuisance, > > who knows).. > > > Anyway, read here for more > > info:http://forums.macrumors.com/showthread.php?t=73360 > > It wasn't caching; I could see the proper file content via Safari's > inspect-element function. > > It turned out that I had to override the content-type to be text/css. > > I *am* going to have to deal with caching, though. As a dynamic page, > it's specifying no caching at all, which is not what you really want > for css. > > > > > -- Julio > > > On Jul 9, 2:16 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > >> I'd like to generate my CSS dynamically, using web2py's views syntax > >> (mainly for macro substitution, dynamic substitution of colors, stuff > >> like that). > > >> So I created a controller named css, with a method called base, and a > >> view named base.css. I then changed layout html to ask for /app/css/ > >> base.css for its stylesheet. > > >> Miraculously, everything works: except that my browser (Safari 4.0.2) > >> won't use the resulting stylesheet, even though, near as I can tell, > >> it looks fine. > > >> Any suggestions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
