summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://kerravonsen.dreamwidth.org/ <http://kerravonsen.dreamwidth.org/@web>2010-03-30 06:44:04 +0000
committerJoey Hess <joey@finch.kitenet.net>2010-03-30 06:44:04 +0000
commit90c444d9f197a5a9b87d3e70248279ac68e351a6 (patch)
treedbaee99655a0404226f9fa8c0362cfaba3a90846
parenta284d5fa0aed7778130f95c9883fe8815ecf37b6 (diff)
response
-rw-r--r--doc/plugins/contrib/report/discussion.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/plugins/contrib/report/discussion.mdwn b/doc/plugins/contrib/report/discussion.mdwn
index 918d0779b..42a1009cb 100644
--- a/doc/plugins/contrib/report/discussion.mdwn
+++ b/doc/plugins/contrib/report/discussion.mdwn
@@ -18,6 +18,17 @@ removing the special case for `field`.
Perhaps the `headers` thing could migrate into inline somehow? That might
lead to making inline too big, though.
+> I think inline is *already* too big, honestly. --[[KathrynAndersen]]
+
Is the intention that the `trail` part is a performance hack, or a way
to select pages? How does it relate to [[todo/wikitrails]] or
[[plugins/contrib/trail]]? --[[smcv]]
+
+> The `trail` part is *both* a performance hack, and a way to select pages. I have over 5000 pages on my site, I need all the performance hacks I can get.
+> For the performance hack, it is a way of reducing the need to iterate through every single page in the wiki in order to find matching pages.
+> For the way-to-select-pages, yes, it is intended to be similar to [[todo/wikitrails]] and [[plugins/contrib/trail]] (and will be more similar with the new release which will be happening soon; it will add prev_* and next_* variables).
+> The idea is that, rather than having to add special "trail" links on PageA to indicate that a page is part of the trail,
+> it takes advantage of the `%links` hash, which already contains, for each page, an array of the links from that page to other pages. No need for special markup, just use what's there; a trail is defined as "all the pages linked to from page X", and since it's an array, it has an order already.
+> But to avoid that being too limiting, one can use a `pages=...` pagespec to filter that list to a subset; only the pages one is interested in.
+> And one can also sort it, if one so desires.
+> --[[KathrynAndersen]]