> I'm not sure I get the idea completely but I see a couple problems. > The big problem is we don't want to lose our ability to edit the css > pages in-wiki. And I don't want to open up the core of BoltWire to > editing pages outside of the pages folder. If we are not worried about > editing it, leave your style sheet in the skin folder, and link to it > directly in the skin. You don't have to use the <<style>> markup in > your skin. We can do this already in BoltWire, easy. > > However, an idea occurred to me that we could use a special kind of > caching system for the main style sheets. When loading the style zone, > we simply check to see if there is a cached copy of the appropriate > style sheet in some css directory. If not we copy it over and generate > a link. If there is one, we check the lastmodified date to see if the > in-wiki page is newer. If it is, we re-cache the css page, and still > generate a link. We could in fact do this for any thing in the << >> > markup, like javascript or whatever. I see some real possibilities > here... Probably a nice boost to performance all the way around.
I really like this suggestion. I would only add that the css-extension would make easier to debug the stylesheet offline on a sample page with a web development software. Bogdan
-- You received this message because you are subscribed to the Google Groups "BoltWire" group. 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/boltwire?hl=en.
