summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorwww-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-05-01 21:26:04 +0000
committerwww-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-05-01 21:26:04 +0000
commitd29786a5fbb69dd10faa6e914a9944b7bc5a592e (patch)
tree6412f4bd45fc633af4dd5f2d048145c187ab35bd /doc
parent6637d5bb25703dd90df0f11085566a7ba958c310 (diff)
web commit by joey
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/plugin.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/todo/plugin.mdwn b/doc/todo/plugin.mdwn
index 1d49de66a..ca3391f8a 100644
--- a/doc/todo/plugin.mdwn
+++ b/doc/todo/plugin.mdwn
@@ -9,7 +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..
+* Support [[RecentChanges]] as a regular page containing a plugin that updates each time there is a change, and statically builds the recent changes list. (Would this be too expensive? There might be other ways to do it as a plugin, like making all links to RecentChanges link to the cgi and have the cgi render it on demand.)
* 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.