3 HTML::Template is an okay templating kit, but it lacks a lot of powerful
4 features and thus makes it rather hard to give an ikiwiki site a consistent
5 look. If you browse the templates provided in the tarball, you'll notice that
6 more than one of them contain the `<html>` tag, which is unnecessary.
8 > Note that is no longer true, and I didn't have to do such an intrusive
9 > change to fix it either. --[[Joey]]
11 Maybe it's just me, I also find HTML::Template cumbersome to use, due in part
12 to its use of capital letters.
14 > Its entirely optional use of capital letters? --[[Joey]]
16 Finally, the software seems unmaintained: the mailing list and searchable
18 <http://html-template.sourceforge.net/html_template.html#frequently%20asked%20questions>
19 are broken and the author has not replied to my query in months.
21 I would love to see ikiwiki use the [Template
22 Toolkit](http://template-toolkit.org/) as templating engine.
24 One major reason for TT is its use of slots, a concept I first encountered
25 with Zope Page Templates and never wanted to miss it again. Let me quickly
26 illustrate, using the HTML::Template syntax for simplicity. Traditionally,
27 templating is done with includes:
30 <TMPL_INCLUDE header> <TMPL_INCLUDE header>
31 this is page A this is page B
32 <TMPL_INCLUDE footer> <TMPL_INCLUDE footer>
34 This involves four pages, and if you mistype "footer" on page B,
35 it'll be broken in potentially subtle ways.
37 Now look at the approach with slots:
45 <TMPL_USE MainTemplate> <TMPL_USE MainTemplate>
46 <TMPL_FILL content> <TMPL_FILL content>
47 This is page A This is page B
48 </TMPL_FILL> </TMPL_FILL>
49 </TMPL_USE> </TMPL_USE>
51 As soon as you think about more structure pages with various slots
52 to fill, I am sure you can see the appeal of that approach. If not,
53 here is some more documentation: <http://wiki.zope.org/ZPT/METALSpecification11>
55 I would be glad to volunteer time to make this switch happen, such as rewrite
56 the templates. I'd prefer not having to touch Perl though...
61 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/)
63 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]]
65 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
67 > HTML::Template allows the use of `<!-- TMPL_SOMETHING ... -->`
68 > instead of `<TMPL_SOMETHING ...>`, see
69 > <http://search.cpan.org/~samtregar/HTML-Template-2.6/Template.pm#NOTES>
70 > for details. I used this PERL regexp to convert my own templates:
72 > s{<\s*(/?TMPL_[A-Z]+)((\s+\w+(=(['"]?)\w+\5)?)+)?\s*/?>}{<!-- $1$2 -->}gi;
74 > (Quoting it properly to use from the shell command-line is
75 > nightmarish, write a script with it.)
78 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
80 > I don't wish HTML::Template to be *replaced* by Template::Toolkit - as
81 > others have said above, it's overkill for my needs. However, I also
82 > agree that HTML::Template has its own problems too. The idea of making
83 > the template system modular, with a choice of which backend to use - I
84 > really like that idea. It would enable me to use some other template
85 > system I like better, such as Text::Template or Text::NeatTemplate. But I
86 > think it would be a lot of work to implement, though perhaps no more work
87 > than making the revision-control backend modular, I guess. One would
88 > need to write an IkiWiki template interface that didn't care what the
89 > backend was, and yet is somehow still flexible enough to take advantage
90 > of special features of different backends. There are an *awful lot* of
91 > things that use templates - not just the `pagetemplate` and `template`
92 > plugins, but a number of others which have specialized templates of their
93 > own. -- [[KathrynAndersen]]a
95 >> A modular template system in ikiwiki is unlikely, as template objects
96 >> are part of the API, notably the `pagetemplate` hook. Unless the other
97 >> system has a compatible template object. --[[Joey]]
99 >>> I hacked an adapter that exposes the HTML::Template API but uses
100 >>> Template::Toolkit for the template rendering. Very rough, but it
101 >>> works: my Wikis compile mostly ok. The code includes a `.tmpl`
102 >>> converter script. Get it from: <http://github.com/riccardomurri/ikiwiki>
103 >>> --[[RiccardoMurri]]
107 >>> I found this thing yesterday:
109 >>> http://search.cpan.org/~rhandom/Template-Alloy-1.016/lib/Template/Alloy.pod
110 >>> I think (hope) this can solve all the problems related to this feature request.
112 >>> From the url above:
113 >>> "With Template::Alloy you can use your favorite template interface and syntax
114 >>> and get features from each of the other major template systems."
projects / ikiwiki / blob