Update test plan, missed in previous.

[git.ikiwiki.info.git] / doc / todo / pagespec_aliases.mdwn

diff --git a/doc/todo/pagespec_aliases.mdwn b/doc/todo/pagespec_aliases.mdwn
index b9bcd109e8024db589c2a87765ca6a3cb2c6475f..748444a2f3801055b5559c2dc47beb30e1f9cf4d 100644 (file)
--- a/doc/todo/pagespec_aliases.mdwn
+++ b/doc/todo/pagespec_aliases.mdwn
@@ -20,9 +20,8 @@ an existing wishlist item.
 
 > I think it would make sense to have "pagespec" in the name somehow.
 
 
 > I think it would make sense to have "pagespec" in the name somehow.
 

-> > Good idea, how about `pagespecalias`? — [[Jon]]
+>> Good idea, how about `pagespecalias`? — [[Jon]]

 
 

->

 > No, the strict/warnings does not make me puke. Have you read my perl
 > code? :-P
 > 
 > No, the strict/warnings does not make me puke. Have you read my perl
 > code? :-P
 > 


@@ -81,11 +80,11 @@ however, to add ' or internal()' to `boring`, for some reason.
 >> Useful indeed! --[[Joey]] 
 
 
 >> Useful indeed! --[[Joey]] 
 
 

->>> I've tweaked my patch in light of your above feedback:  The plugin has
->>> been renamed, and I now validate keys.  I've also added documentation to
->>> the branch.  I haven't read rubykat's code properly yet, and don't have
->>> access at the time of writing (I'm on a beach in Greece ☺), but I expect
->>> it would be possible to extend what I've got here to support defining the
+>>> I've tweaked my patch in light of your above feedback:  The plugin has been
+>>> renamed, and I now validate keys.  I've also added documentation and tests
+>>> to the branch.  I haven't read rubykat's code properly yet, and don't have
+>>> access at the time of writing (I'm on a beach in Greece ☺), but I expect it
+>>> would be possible to extend what I've got here to support defining the

 >>> aliases in a PageSpec, once the dependency stuff has been reasoned out
 >>> properly.
 >>>
 >>> aliases in a PageSpec, once the dependency stuff has been reasoned out
 >>> properly.
 >>>


@@ -93,6 +92,18 @@ however, to add ' or internal()' to `boring`, for some reason.
 >>> implementing support for more nested datatypes in [[plugins/websetup]]. —
 >>> [[Jon]]
 
 >>> implementing support for more nested datatypes in [[plugins/websetup]]. —
 >>> [[Jon]]
 

+>>>> Well, it's a difficult problem. websetup builds a form using
+>>>> CGI::FormBuilder, which makes it easy to build the simple UI we have
+>>>> now, but sorta precludes anything more complicated. And anything with
+>>>> a nested datatype probably needs a customized UI for users to be able
+>>>> to deal with it. I don't think websetupability need be a deal-breaker
+>>>> for this patch. I personally like special pages like Kathryn is doing
+>>>> more than complex setup files. --[[Joey]]
+
+>>>>> I've ran out of time to keep working on this, so I'm just going to
+>>>>> submit it as a 'contrib' plugin and leave things at that for now.
+>>>>> — [[Jon]]
+

 ---------------------------
 
 Based on the above, I have written an experimental plugin called "subset".
 ---------------------------
 
 Based on the above, I have written an experimental plugin called "subset".


@@ -151,3 +162,8 @@ Unfortunately I haven't figured out how to do the dependencies - I'd really appr
 >>>> whatever you like ☺  I like some of the enhancements you've made, but
 >>>> having the aliases/subsets/"things" work in any pagespec (inside map, or
 >>>> inline) is a deal-breaker for me. — [[Jon]]
 >>>> whatever you like ☺  I like some of the enhancements you've made, but
 >>>> having the aliases/subsets/"things" work in any pagespec (inside map, or
 >>>> inline) is a deal-breaker for me. — [[Jon]]

+
+>>>>> I'm a bit confused by your statement "having the aliases/subsets/"things" work in any pagespec (inside map, or inline) is a deal-breaker for me".
+>>>>> Do you mean that you want them to work in any pagespec, or that you *don't* want them to work in any pagespec? -- [[KathrynAndersen]]
+
+>>>>>> I mean I would want them to work in any pagespec. — [[Jon]]