You're missing the point.
HTML::Template doesn't aspire to be anything like Template Toolkit. Deliberately. They fill completely different roles. Mason fills a third role.
- HTML::Template is designed to do one thing - be fast. Be very, very fast. It has extremely few things it can do, but it does those things very well. It's a mark of how well samtregar designed it that it's used in as many places and in as many ways as it is.
- Template Toolkit is designed to do one thing - be very easy to work with. And, it does this very well. It renders very fast, but that's not its primary goal. It's primary goal is ease of abstraction. And, it does this very well.
- Mason isn't designed to be a templating system. It's a Content Management System, similar to Asgard and many others. It's a mark of its strong design that it can be used solely as a templating system. And, like the others, it does CMS very well.
You can't even abstract out common functionality. I'm in the process of looking to convert my apps from H::T to TT because I need the additional functionality. (Most apps will never need this functionality.) I'm finding that the very code I'll be using to generate the data structures for TT is going to be different than the code used for H::T. In many cases, up to 80% different.
This isn't an indictment of H::T. In fact, when I first started work on these apps, I knew I would convert to TT at some point. I used H::T for its strenth - speed of initial development. I know it inside and out. I could throw it out there and not worry about it.
TT, on the other hand, requires a lot of thought and up-front design. I didn't know enough about what I would want, nor could I gather that information in the initial 6 weeks I was given to make everything work. Now, I do know enough, so I can do my design and convert my apps.
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.