On Thu, Jan 7, 2010 at 7:48 PM, Erlend Sogge Heggen <[email protected]> wrote: > I believe Wordpress has been praised countlessly for its application > of this standard. Just looking at the amount of free top notch > Wordpress themes around they must have done something to make a lot of > web developers happy. Might be worth looking into a couple Wordpress > theme tutorials.
If anyone cares to do the research and share their findings that might be helpful... > On Jan 8, 1:02 am, DrunkenMonk <[email protected]> wrote: >> is it really that hard? >> >> consider the following system: >> * the group code.css are looked for in a different folder (I believe >> there was support for that allready, but a rewrite rule to map >> code.css.pagename to $$pub/css/pagename.css might be handy. Perhaps >> even map code.css.page.name to $$pub/css/page/name.css to allow easy >> css file organisation) >> * a command [(css pagename)], placed in the header or similar, to add >> a .css file to the end of the css list. (Theres a list, right? You add >> or replace the last placed commands, the rest are inherited? :p) >> and done? Well, you get the picture. 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. Cheers, Dan
-- 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.
