aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/recentchanges.mdwn
blob: 71b9dfed63be19a19712a7d6f47f6478d067c574 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
* 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. --[[Joey]]

* 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.. --[[Joey]]

* 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.

  > That would work rather well for pages like [[todo]] and [[bugs]], where
  > you want to know about any updates, not just initial
  > creation. --[[JoshTriplett]]

  > Of course you can use email subscriptions for that too.. --[[Joey]]

  >> I have more thoughts on this topic which I will probably write 
  >> tomorrow. If you thought my other patches were blue-sky, wait until 
  >> you see this. --Ethan