My web customers, some who are HTML savvy, were asking for the ability to edit their HTML, which I had previously buried in CGI scripts. For precisely the reason mentioned previously, I switched to H::T. If I'm careful, I use H::T to simply fill in data from the MySQL database, but if I'm not careful, I find myself using H::T to actually write custom HTML, with the data embedded, to the template, thus, defeating the purpose.

The challenge for me, then, is to write more clever HTML or CGI to keep H::T doing what it's supposed to do.

I find no other downsides to using H::T, at least in terms of performance. Although like using any module, I feel a little guilty that it's so easy to use someone else's hard wrought code.

All in all, H::T is a winner for me.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.