From a632e366a06c61de7d7a60dbe5d552c65a83d00e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 5 Mar 2008 10:01:52 -0500 Subject: web commit by http://subvert.org.uk/~bma/: Argument in favour of Varioki over creating new plugins to set template variables. --- ...es___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc/todo') diff --git a/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn b/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn index 431305622..c5fe28f4b 100644 --- a/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn +++ b/doc/todo/varioki_--_add_template_variables___40__with_closures_for_values__41___in_ikiwiki.setup.mdwn @@ -47,6 +47,15 @@ ManojSrivastava }, +> > I'd argue in favour of this plugin; it's true that a simple plugin can be +> > used to set a template variable, but that makes it necessary to write a new +> > plugin for every variable (or set of variables) that are needed. In that +> > kind of situation, I don't think bypassing the plugin mechanism is a bad +> > thing, unless an ever-growing collection of plugins to set one or two +> > variables is a good thing. +> > +> > --[[bma]] + ---- 
-- 
cgit v1.2.3