summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRocco <Rocco@web>2009-01-25 03:39:52 -0500
committerJoey Hess <joey@kitenet.net>2009-01-25 03:39:52 -0500
commit31a6f1735cf98a565a82b7cc720d6b2e8e49ad13 (patch)
tree5f939aacf09e05e3e117f379c2a3bfc817b8df07
parenta6eb921b9dfdfe8b1299b354885a0ee1dbe90a9c (diff)
vote for Template::Toolkit
-rw-r--r--doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
index 3b9f6c0fd..c4e78ca0b 100644
--- a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
+++ b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn
@@ -56,3 +56,5 @@ 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