Template Toolkit is an an entire mini-language which can lead to bad practices and runs slower than most, if not all, of the other template kits while HTML::Template more strictly adheres to the purist idea of what a View RFC:SHOULD be. That sounds like a good thing at first but it hinders you, lacking all but the most simplistic loop controls and unsweetened include directives; and speed in the template layer is rarely a real issue in the full stack of a live web application.
If the Template Toolkit route is appealing to you, you should know that it includes its own caching and dozens of other really nice affordances which will make your development easier, more fun and, if you can restrain yourself from going PHP on your templates, plenty manageable.
:P — see also Template::Alloy for Template (TT2) compatible syntax with some of TT3 too.
If you do want to go PHP on your templates, see Mason. But I keed!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||