From a1b5dec5fc46863210934252f84331a057ade477 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 15 Jul 2008 05:37:29 -0400 Subject: [PATCH] web commit by intrigeri: pedigree: compromise? --- doc/todo/pedigree_plugin.mdwn | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/doc/todo/pedigree_plugin.mdwn b/doc/todo/pedigree_plugin.mdwn index 120820d03..7b0aa81a4 100644 --- a/doc/todo/pedigree_plugin.mdwn +++ b/doc/todo/pedigree_plugin.mdwn @@ -133,6 +133,29 @@ Any opinions on the idea/design/implementation? >>>> the loop using HTML::Template's lame testing, and isolate any page or >>>> range of pages. --[[Joey]] +>>>>> Ok, I definitely like this idea, as an effective and generic +>>>>> page-range selection tool; this seems the way to go to me. + +>>>>> But if you discard the `DEPTH` and `HEIGHT` +>>>>> counters, we lack a way to **style**, for example, every parent link +>>>>> depending on its depth or height; one can do this for arbitrary +>>>>> parents (chosen by their height or depth), but *not* for *any* parent, +>>>>> since there is no way to express, with HTML::Template, something like +>>>>> "display the name of the only `DEPTH_n` variable that is currently +>>>>> true". So I am in favor of keeping the `DEPTH` and `HEIGHT` counters, +>>>>> to allow constructs like: + + + " class="parentdistance"> + + / + + +>>>>> This seems to me a nice functionality bonus, and should not +>>>>> imply too bloated code. I'm thus going to rewrite the plugin +>>>>> with only `PEDIGREE`, `DEPTH`, `HEIGHT`, `DEPTH_n` and +>>>>> `HEIGHT_n`. -- intrigeri + (I'll try never to rebase this branch, but writing this plugin has been a pretext for me to start learning Git, so...) -- 2.26.2