It's basically a matter of how you need to weight different aspects of your project. If you're project is pretty simple, and your outputs similar, then it probably doesn't matter. If your outputs are very different then you will run into a complexity problem very quickly. In my experience making a generic master template tends to lead to the HTML dicatating how you write your Perl code, and the more generic, the most this tends to hold true - Now HTML becomes the master of the Perl script. Probably the best trade off (as was mentioned before) is to use <TMPL_IF> and <TMPL_INCLUDE>. You add another layer of abstraction in a way, but it will probably be the most maintanable and offers the most ballence.

In reply to Re: HTML::Template - what's the rule of thumb? by Anonymous Monk
in thread HTML::Template - what's the rule of thumb? by kiat

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.