Merge remote branch 'upstream/master' into prv/po

[git.ikiwiki.info.git] / doc / todo / replace_HTML::Template_with_Template_Toolkit.mdwn

diff --git a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
index c73b53e53f338264a318e866599364b10bcdd45f..c4e78ca0bb7147eba8765b5185820f3beb279eda 100644 (file)
--- a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
+++ b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
@@ -1,4 +1,4 @@
-[[tag wishlist]]
+[[!tag wishlist]]
 
 HTML::Template is an okay templating kit, but it lacks a lot of powerful
 features and thus makes it rather hard to give an ikiwiki site a consistent
@@ -54,3 +54,7 @@ the templates. I'd prefer not having to touch Perl though...
 -----
 
 Yes, Template::Toolkit is very powerful. But I think it's somehow overkill for a wiki. HTML::Template can keep things simple, though.  --[weakish](http://weakish.int.eu.org/blog/)
+
+I'd have to agree that Template::Toolkit is overkill and personally I'm not a fan, but it is very popular (there is even a book) and the new version (3) is alleged to be much more nimble than current version.  --[[ajt]]
+
+HTML::Template's HTML-like markup prevents me from editing templates in KompoZer or other WYSIWYG HTML editors.  The editor tries to render the template markup rather than display it verbatim, and large parts of the template become invisible.  A markup syntax that doesn't confuse editors (such as Template::Toolkit's "[% FOO %]") may promote template customization.  The ability to replace the template engine would be within the spirit of ikiwiki's extensibility. --Rocco