The use case I'm looking at is someone who wants to use PHP for their theme, put put HiEngine variables in the CSS.
On Apr 28, 2009, at 9:35 AM, Owen Winkler wrote: > > On Mon, Apr 27, 2009 at 10:37 PM, Arthus Erea > <[email protected]> wrote: >> >> Would we have to store the "current" querystring in the database? > > That or we could hash the date of the cached file and use that as the > querystring. Storing it in the database would likely be more > efficient. > >> >> There were objections to forcing people to use HiEngine if they would >> prefer PHP. >> >> Personally, I see a lot of benefit in being able to use more complex >> PHP (if need be) within stylesheets, and it doesn't seem to >> complicate >> the process any of themers. > > That's fine, but there are two points to make: > > 1) HiEngine themes already run PHP. Put PHP in a HiEngine theme and > it works normally. If you object to it, don't use it. Or do use it > because PHP still works normally there. Right, could we use the same system to parse the HiEngine syntax in the css, while also allowing PHP? > 2) If the themer makes the choice to use HiEngine for his theme, then > it makes sense that his css processing can also be handled by > HiEngine. Of course, but I think PHP themers should still be able to use HiEngine in their theme. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
