1 I've found myself wanting to know which [[plugins]] are switched on so I know which pre-processor commands I can use. The attached [[patch]] adds a new plugin that generates the list of available plugins. -- [[Will]]
3 > Good idea, I do see a few problems:
5 > - preprocessor directives do not necessarily have the same name as the
6 > plugin that contains them (for example, the graphviz plugin adds a graph
7 > directive). Won't keys `%{IkiWiki::hooks{preprocess}}` work?
9 >>> Er, yeah - that's a much better solution. :) -- and done
11 > - "listplugins" is a bit misnamed since it only does preprocessor directives.
13 >>> Yes. Initially this was going to list all enabled plugins. Then when searching
14 >>> for enabled plugins I changed my mind and decided that a list of pre-processor
15 >>> directives was more useful. I'll fix that too. -- changed to `listpreprocessors`
17 > - comment was copied from version plugin and still mentions version :-)
21 > - Seems like [[ikiwiki/formatting]] could benefit from including the
22 > list.. however, just a list of preprocessor directive names is not
23 > the most user-friendly thing that could be put on that page. It would
24 > be nice if there were also a short description and maybe an example of
25 > use. Seems like the place to include that info would be in the call
27 > (Maybe adding that is more involved than you want to go though..)
31 >> Adding a whole new hook for a usage example is more effort than I
32 >> wanted to go to. I was thinking of either:
34 >>> Just to clarify, I meant adding new parameters to the same hook call
35 >>> that registers the plugin. --[[Joey]]
37 >> - Adding a configuration for a wiki directory. If a matching page is in the
38 >> specified wiki directory then the plugin name gets turned into a link to that
40 >> - Adding configuration for an external URL. Each plugin name is added as
41 >> a link to the plugin name appended to the URL.
43 >>The first option is easier to navigate and wouldn't produce broken links,
44 >>but requires all the plugin documentation to be local. The second option
45 >>can link back to the main IkiWiki site, but if you have any non-standard
46 >>plugins then you'll get broken links.
48 >>Hrm. After listing all of that, maybe your idea with the hooks is the better
49 >>solution. I'll think about it some more. -- [[Will]]
51 >>> I've also run into this problem with the websetup plugin, and
52 >>> considered those ideas too. I don't like the external url, because
53 >>> ikiwiki.info may be out of sync with the version of ikiwiki being used.
54 >>> (Or maybe it's gone! :-) The first idea is fine, except for the bloat
55 >>> issue. If turning on listpreprocessors and/or websetup means adding
56 >>> hundreds of pages (and of kilobytes) to your wiki, that could be an
57 >>> incentive to not turn them on..
59 >>> Hmm.. maybe the thing to do is to use _internal pages for the plugins;
60 >>> then the individual pages would not be rendered, and your inlines would
61 >>> still work. Although I don't know how websetup would use it then, and
62 >>> also they would have to be non-internal for ikiwiki's own docwiki. Hmm.
63 >>> Maybe these are two different things; one is a set of pages describing
64 >>> preprocessor directives, and the second a set of pages describing
65 >>> plugins. They're so closely related though it seems a shame to keep
69 >>> I started implementing the hook based solution, and decided I didn't like
70 >>> it because there was no nice way to rebuild pages when the preprocessor
71 >>> descriptions changed. So instead I assumed that the the [[plugins]] pages
72 >>> would be moved into the underlay directory. This plugin then uses an
73 >>> `inline` directive to include those pages. You can use the `inline`
74 >>> parameter to decide if you want to include all the descriptions or
75 >>> just the titles. There is also an option to auto-create default/blank
76 >>> description pages if they are missing (from a template). As preprocessor
77 >>> commands don't list unless they have a description page, auto-creation
78 >>> is enabled by default.
80 >>> There are three new templates that are needed. These are for:
82 >>> - The auto-created description pages are generated from `preprocessor-description.tmpl`.
83 >>> - When only pre-processor names are listed, the `listpreprocessors-listonly.tmpl` template is used.
84 >>> - When pre-processor descriptions are included inline, the `listpreprocessors-inline.tmpl` template is used.
88 >>>> Just a quick note: pages are only created for pre-processor commands
89 >>>> that exist when the `refresh` hook is called. This is before the [[shortcuts]] are
90 >>>> processed. However, the list of available pre-processor commands will include
91 >>>> shortcuts if they have description pages (the list is generated later, after the
92 >>>> shortcuts have been added). While this was unplanned, it seems a reasonable
93 >>>> tradeoff between including all the large number of shortcuts and including none. -- [[Will]]
95 >>>>>> I think that using an inline is elegant! However, I don't understand
96 >>>>>> why it has to create stub description pages? I doubt that, if a
97 >>>>>> directive is missing a page, the stub will be filled out in many
98 >>>>>> wikis. And it adds a lot of complexity, particularly committing a
99 >>>>>> bunch of generated pages to revision control when the user just
100 >>>>>> wants a plugin list seems undesirable.
102 >>>>>> Seems to me it could use the inline for pages that exist, and append
103 >>>>>> to the bottom a generated text for anything that is currently missing.
104 >>>>>> The generated text could even have a page creation link in it if
108 >>>>>>> I kinda agree about the page generation. I don't like mixing an
109 >>>>>>> inlined and a list though. Besides which, that ends
110 >>>>>>> up keeping much of complexity of the page generation because
111 >>>>>>> the code still has to detect which pages are missing. I've added
112 >>>>>>> a patch that uses a list of wikilinks instead. This way available
113 >>>>>>> pages get linked correctly, and missing pages get normal creation
114 >>>>>>> links. The old patch is still here if you decide you prefer that. -- [[Will]]
116 >>>>>>>> Can you explain the full/early list (why track both?) and generated parameter?
117 >>>>>>>> Only code change I'd suggest is using `htmllink` rather than
118 >>>>>>>> generating a wikilink.
121 # Ikiwiki listpreprocessors plugin.
122 package IkiWiki::Plugin::listpreprocessors;
129 hook(type => "getsetup", id => "listpreprocessors", call => \&getsetup);
130 hook(type => "checkconfig", id => "listpreprocessors", call => \&checkconfig);
131 hook(type => "needsbuild", id => "listpreprocessors", call => \&needsbuild);
132 hook(type => "preprocess", id => "listpreprocessors", call => \&preprocess);
135 sub getsetup () { #{{{
141 preprocessor_description_dir => {
143 description => "The ikiwiki directory that contains plugin descriptions.",
153 sub checkconfig () { #{{{
154 if (!defined $config{plugin_description_dir}) {
155 $config{plugin_description_dir} = "ikiwiki/plugin/";
158 @earlyPluginList = sort( keys %{ $IkiWiki::hooks{preprocess} } );
161 sub needsbuild (@) { #{{{
162 my $needsbuild=shift;
164 @fullPluginList = sort( keys %{ $IkiWiki::hooks{preprocess} } );
165 $pluginString = join (' ', @earlyPluginList) . " : ". join (' ', @fullPluginList);
167 foreach my $page (keys %pagestate) {
168 if (exists $pagestate{$page}{listpreprocessors}{shown}) {
169 if ($pagestate{$page}{listpreprocessors}{shown} ne $pluginString) {
170 push @$needsbuild, $pagesources{$page};
172 if (exists $pagesources{$page} &&
173 grep { $_ eq $pagesources{$page} } @$needsbuild) {
174 # remove state, will be re-added if
175 # the [[!listpreprocessors]] is still there during the
177 delete $pagestate{$page}{listpreprocessors}{shown};
183 sub preprocess (@) { #{{{
186 $pagestate{$params{destpage}}{listpreprocessors}{shown}=$pluginString;
190 if (! defined $params{generated}) {
191 @pluginlist = @fullPluginList;
193 @pluginlist = @earlyPluginList;
196 my $result = '<ul class="listpreprocessors">';
198 foreach my $plugin (@pluginlist) {
199 $result .= '<li class="listpreprocessors">[[' . $config{plugin_description_dir} . $plugin . ']]</li>';
204 return IkiWiki::preprocess($params{page}, $params{destpage},
205 IkiWiki::filter($params{page}, $params{destpage}, $result));
212 Here is the main listpreprocessors plugin. (Note, because this has double
213 square brackets in the source, it isn't quite displaying correctly - look
214 at the page source for details.) New template files follow:
217 # Ikiwiki listpreprocessors plugin.
218 package IkiWiki::Plugin::listpreprocessors;
226 hook(type => "getsetup", id => "listpreprocessors", call => \&getsetup);
227 hook(type => "preprocess", id => "listpreprocessors", call => \&preprocess);
228 hook(type => "refresh", id => "listpreprocessors", call => \&refresh);
231 sub getsetup () { #{{{
237 preprocessor_description_dir => {
239 description => "The ikiwiki directory that contains plugin descriptions.",
243 preprocessor_description_autocreate => {
245 description => "Should pre-processor command descriptions be automatically created from a template.",
251 sub gendescription ($$) { #{{{
254 my $file=$page.".".$config{default_pageext};
255 my $template=template("preprocessor-description.tmpl");
256 $template->param(page => $page, plugin => $plugin);
257 writefile($file, $config{srcdir}, $template->output);
259 IkiWiki::rcs_add($file);
263 sub refresh () { #{{{
264 eval q{use File::Find};
267 if (defined $config{preprocessor_description_autocreate} && ! $config{preprocessor_description_autocreate}) {
268 return; # create pages unless they explicitly ask us not to
271 if (!defined $config{preprocessor_description_dir}) {
272 $config{preprocessor_description_dir} = "ikiwiki/plugin/";
275 my @pluginlist = sort( keys %{ $IkiWiki::hooks{preprocess} } );
281 foreach $plugin (@pluginlist) {
282 $pluginpages{$plugin} = $config{preprocessor_description_dir} . $plugin;
286 foreach my $dir ($config{srcdir}, @{$config{underlaydirs}}, $config{underlaydir}) {
291 if (IkiWiki::file_pruned($_, $dir)) {
292 $File::Find::prune=1;
295 my ($f)=/$config{wiki_file_regexp}/; # untaint
296 return unless defined $f;
297 $f=~s/^\Q$dir\E\/?//;
298 return unless length $f;
299 return if $f =~ /\._([^.]+)$/; # skip internal page
301 $pages{pagename($f)}=$f;
309 IkiWiki::disable_commit_hook();
314 while (($plugin,$page) = each %pluginpages) {
315 if (! exists $pages{$page}) {
317 gendescription($plugin,$page);
323 IkiWiki::rcs_commit_staged(
324 gettext("automatic pre-processor description generation"),
327 IkiWiki::enable_commit_hook();
332 sub preprocess (@) { #{{{
335 if (!defined $config{plugin_description_dir}) {
336 $config{plugin_description_dir} = "ikiwiki/plugin/";
339 my @pluginlist = sort( keys %{ $IkiWiki::hooks{preprocess} } );
340 foreach my $plugin (@pluginlist) {
341 $plugin = $config{plugin_description_dir} . $plugin;
343 my $pluginString = join (' or ', @pluginlist);
345 my $result = "[[!inline pages=\"$pluginString\" feeds=\"no\" show=0 sort=\"title\"";
347 if (defined $params{inline}) {
348 $result .= ' template=\"listpreprocessors-listonly\" archive="yes"';
350 $result .= ' template=\"listpreprocessors-inline\" archive="no"';
355 return IkiWiki::preprocess($params{page}, $params{destpage},
356 IkiWiki::filter($params{page}, $params{destpage}, $result));
363 This is what I was using for `listpreprocessors-inline.tmpl`:
365 <div class="listpreprocessorsinline">
367 <div class="inlineheader">
369 <span class="header">
370 <a href="<TMPL_VAR PAGEURL>"><TMPL_VAR TITLE></a>
373 </div><!--.inlineheader-->
375 <div class="inlinecontent">
377 </div><!--.inlinecontent-->
379 </div><!--.listpreprocessorsinline-->
383 This is what I was using for `listpreprocessors-listonly.tmpl`:
385 <p class="listpreprocessors"><a href="<TMPL_VAR PAGEURL>"><TMPL_VAR TITLE></a></p>
389 This is what I was using for `preprocessor-description.tmpl`:
391 The <TMPL_VAR plugin> preprocessor command currently has no description.
393 Maybe you should edit this page to add one.