web commit by joey

[www/ikiwiki.git] / doc / todo / plugin.mdwn

diff --git a/doc/todo/plugin.mdwn b/doc/todo/plugin.mdwn
index 8b1487df2e2213f18cfca4e2afcfa26d7dcc15f8..1d49de66a19d78ac02e1c6f5550f16ded802d9b6 100644 (file)
--- a/doc/todo/plugin.mdwn
+++ b/doc/todo/plugin.mdwn
@@ -9,6 +9,7 @@ A plugin system should ideally support things like:
 * Wiki stats, such as the total number of pages, total number of links, most linked to pages, etc, etc.
 * wiki info page, giving the ikiwiki version etc
 * would it be useful to reimplement the hyperestradier search integration as a plugin?
+* Maybe it would be possible to make RecentChanges a regular wiki page, by making it a page that renders statically, but somehow runs the cgi at view time to dyamically render the changes? Then this could be a plugin too. How would this be accomplished in html though? Only way I know is via server side includes..
 * etc
 
 Another, separate plugin system that already (mostly) exists in ikiwiki is the RCS backend, which allows writing modules to drive other RCS systems than subversion.
@@ -33,6 +34,3 @@ See <http://moinmoin.wikiwikiweb.de/MoinDev/PluginConcept>
 * *parsers* and *formatters* are basically what I've been calling [[PluggableRenderers]]. MoinMoin separates these, so that a page is parsed to (presumbly) some intermediate form before being output as html or some other form. That's a nice separation, but what to do about things like markdown that are both a parser and a formatter?
 * *macros* and *processors* are analagous to preprocessor directives. A processor can operate on a large block of text though.
 * *themes* should be irrellevant (ikiwiki has [[templates]]).
-
-## case study: pybloxsom plugins
-