diff options
| author | http://churchkey.org/author/ian/ <http://churchkey.org/author/ian/@web> | 2010-11-15 15:50:37 +0000 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2010-11-15 15:50:37 +0000 |
| commit | f6312319a49cc1860eebbafd937a0f75d8e7baeb (patch) | |
| tree | cdd09faff682c76f8737c6c625d5d8a1c1c936ff | |
| parent | 84fff62948ad7c7aef664585e8afed86398e7fd4 (diff) | |
added my reasons for wanting a replace-able template system
| -rw-r--r-- | doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn | 3 |
1 files changed, 3 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 c4e78ca0b..8650e4f2a 100644 --- a/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn +++ b/doc/todo/replace_HTML::Template_with_Template_Toolkit.mdwn @@ -58,3 +58,6 @@ Yes, Template::Toolkit is very powerful. But I think it's somehow overkill for a 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 + + +I agree that being able to replace the template toolkit would be a great piece of modularity, and one I would use. If I could use the slot-based filling and the conditional logic from Template::Toolkit, we could build much more flexible inline and archivepage templates that would look different depending on where in the wiki we use them. Some of this can currently be accomplished with separate templates for each use case and a manual call to the right template in the !inline directive, but this is limited, cumbersome, and makes it difficult to reuse bits of formatting by trapping all of that information in multiple template files. -Ian |