re-generating on options save seems like the best option to me, but there is an issue with tinkerers who want to tweak the CSS manually. Perhaps if it re-generated when the options are saved or when the save date of the base CSS file altered? What kind of hit would that bring?
The Hi engine syntax seems no less complex than anything else that might be in place so I don't see any harm in using that for the CSS replacement. 2009/4/27 Rich Bowen <rbo...@rcbowen.com>: > > > On Apr 27, 2009, at 09:56, Owen Winkler wrote: > >> Assume you have a cache directory at /user/build. The theme would >> output the stylesheet URL as /user/build/style.css (for example). >> This >> file does not yet exist in the directory. >> >> Because the file does not exist, the request is routed through Habari. >> Habari, using rewrite rules that catch requests to the build cache, >> notes the request and builds the file. The file is served, but is >> also >> saved into the correct location in the cache directory. >> >> The result is that on the next request, the file exists. Apache sees >> that the file exists and serves it directly instead of routing through >> Habari. The file is served much faster because there is no PHP >> processing. > > > > ++1 > > Or a great big "REGENERATE THEME" button. Having to generate anything > on the fly, every time, when it's exactly the same every time, is a > waste of my precious milliseconds. > > > -- > I have nature and art and poetry, > and if that is not enough, what is enough? > (Vincent van Gogh) > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to habari-dev@googlegroups.com To unsubscribe from this group, send email to habari-dev-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
