Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This sounds to me like a case of using the wrong tool for the job. HTML::Template was designed to support a workflow wherein a Perl geek codes Perl and an HTML designer designs in HTML. The template syntax is kept simple so that the HTML designer doesn't have to learn a whole new language just to create a template. All the code goes in one place and all the HTML goes in another. It's nirvana when you reach it, but there's no way to get there alone.

    However, it sounds to me like you're a lone Perl geek

    • Then Template Toolkit does H::T's job better.

      A designers using TT won't need to know any more than a designer using H::T.

      But at the same time the same templates can acheive a great deal more without the ridiculous hoop jumping required with H::T.

      A designer should not have to worry about many of the problems H::T brings with it. Scoping of variables and other problems make many simple HTML layout tasks hard or impossible.

      This is why I think I that H::T is lame - it doesn't even do HTML Templating very well - which is what it claims to do on the tin.

      The FAQ and documentation is thin on the ground and essential features are lacking such as template variables, the ability to get keys from hashes and the usability of TT.

      I don't mean to slag off the product of somebodies work, but it quite simply doesn't deliver what its advocates or developers claim. The FAQ should give a long list of things that H::T can't do or makes difficult.

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • Enlighten me then, where should I start in the "long list of things that H::T can't do"? I can't think of a single HTML task I haven't been able to with HTML::Template. I build web applications all day long with HTML::Template and CGI::Application, and nothing has stopped me yet!

        -sam

        • ok try looping through N lists concurrently, or looping through the keys of a hash, or using an iterator object, or keeping track of presentation logic values with variables local to the template.

          You can do anything with H::T assuming you totally mangle your data and code to squeeze everything into an array of hashes.

          --

          @JAPH = qw(Hacker Perl Another Just);
          print reverse @JAPH;