summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorhttp://www.cse.unsw.edu.au/~willu/ <http://www.cse.unsw.edu.au/~willu/@web>2008-08-24 17:29:52 -0400
committerJoey Hess <joey@kitenet.net>2008-08-24 17:29:52 -0400
commit7465e0dd5d3b567076aa0cc8101c35eb26eab22f (patch)
tree34cc862c90ef311d52a803dc8db2f9ce38609431 /doc
parent69e35d3c515cd30c9baf82468008d0b0643e1e1f (diff)
Response
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Add_a_plugin_to_list_available_pre-processor_commands.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/todo/Add_a_plugin_to_list_available_pre-processor_commands.mdwn b/doc/todo/Add_a_plugin_to_list_available_pre-processor_commands.mdwn
index 951ebe999..e311addcd 100644
--- a/doc/todo/Add_a_plugin_to_list_available_pre-processor_commands.mdwn
+++ b/doc/todo/Add_a_plugin_to_list_available_pre-processor_commands.mdwn
@@ -114,9 +114,29 @@ I've found myself wanting to know which [[plugins]] are switched on so I know wh
>>>>>>> links. The old patch is still here if you decide you prefer that. -- [[Will]]
>>>>>>>> Can you explain the full/early list (why track both?) and generated parameter?
+
+>>>>>>>>> If you add in all the shortcuts you get quite a long list. My original idea
+>>>>>>>>> was to just track the plugin commands. This is the early list. But then
+>>>>>>>>> I thought that it might be nice for someone looking at wiki source and
+>>>>>>>>> seeing a shortcut to know where it came from. So I decided to make
+>>>>>>>>> displaying the full list an option, with the original concept as the default.
+
+>>>>>>>>> Another option here might be to generate the full list every time, but give
+>>>>>>>>> generated pre-processor commands (e.g. shortcuts) a different css class.
+>>>>>>>>> I'm not sure that is better than what I have though.
+
+>>>>>>>>> I keep track of both in the page state because if a command moves from
+>>>>>>>>> a shortcut to the early list (or vice versa) it changes what should be
+>>>>>>>>> displayed in the default use of the plugin. I thought about tracking just what
+>>>>>>>>> was actually used on the page, but I don't know in the needsbuild hook whether the `generated`
+>>>>>>>>> parameter has been supplied (or maybe the plugin is used twice on the page -
+>>>>>>>>> once in each form). It was just easier to track both.
+
>>>>>>>> Only code change I'd suggest is using `htmllink` rather than
>>>>>>>> generating a wikilink.
+>>>>>>>>> Yeah - that would make sense. Will do. -- [[Will]]
+
#!/usr/bin/perl
# Ikiwiki listpreprocessors plugin.
package IkiWiki::Plugin::listpreprocessors;