From bf4e6716cc57eb6d0dfca43ce92b64934950513e Mon Sep 17 00:00:00 2001 From: joey Date: Sun, 8 Oct 2006 22:27:48 +0000 Subject: responses and reorg --- doc/todo/recentchanges.mdwn | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/todo/recentchanges.mdwn (limited to 'doc/todo') diff --git a/doc/todo/recentchanges.mdwn b/doc/todo/recentchanges.mdwn new file mode 100644 index 000000000..7337c3d49 --- /dev/null +++ b/doc/todo/recentchanges.mdwn @@ -0,0 +1,23 @@ +* Why isn't it statically-genereated, but generated dynamically by CGI? It + seems like it could be beneficial to have it rendered in the post-commit + hook, just like everything else in the wiki. + + I hope to statically generate it eventually, currently the problem is + that it takes at least several seconds to generate the recentchanges + page, and adding several seconds to every page edit is not desiriable. If + the time can be reduced it could be done, I'm also not adverse to + adding an optional way to statically render it even at the current speed. + +* Also, is it planned/desired that recent changes generate the same + information in RSS feed format? This seems like it could be a useful way + to keep track of the wiki as a whole. + + This is used by various interwiki type things, I think, so should be + done.. + +* Lastly, would it be possible to use the recent changes code with a + pagespec? I understand this sort of infringes on territory covered by the + inline plugin, but the inline plugin only puts a page in the RSS feed + once, when it's created, and I imagine some people -- some deranged, + obsessive-compulsive people like myself -- would like to know about the + changes made to existing pages as well as newly-created pages. -- cgit v1.2.3