From: http://lovesgoodfood.com/jason/ Date: Mon, 7 Mar 2011 01:47:33 +0000 (+0000) Subject: Idea for extending inline. X-Git-Tag: 3.20110321~12^2~4 X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/commitdiff_plain/a47d8b343b1b8f8c488c3850ac065999e700648c?ds=sidebyside;hp=5e08848189b96ac772a6e581eb51bde9c7a9bae6 Idea for extending inline. --- diff --git a/doc/ikiwiki/directive/inline/discussion.mdwn b/doc/ikiwiki/directive/inline/discussion.mdwn index 6a186cd93..8f74b100d 100644 --- a/doc/ikiwiki/directive/inline/discussion.mdwn +++ b/doc/ikiwiki/directive/inline/discussion.mdwn @@ -132,6 +132,14 @@ Else can you please suggest a smarter way of getting certain data out from pages --[[hendry]] +## A different idea: smuggling hook routines in through %params. + +The part that fetches the inlined content is quite compact. It's just the if ($needcontent) {} chunk. Would a patch that accepts a perl sub smuggled through something like $params{inliner_} be accepted? If that param exists, call it instead of the current content of that chunk. Pass $page, %params, and $template. Receive $content, possibly seeing $template modified. The custom directives can add inliner_ to %params and call IkiWiki::preprocess_inline. I suppose IkiWiki::Plugin::inline could be modified to strip any *_ out of the directive's arguments to prevent any custom behavior from leaking into the inline directive. + +I'm about to try this for a CV/resume type of thing. I want only one element with a specific id out of the generated content (with a little post-processing). I don't need performance for my case. + +--[[JasonRiedy]] + --- ## Interaction of `show` and `feedshow`