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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Wrong tool for the job? (Score:2)
However, it sounds to me like you're a lone Perl geek
Re:Wrong tool for the job? (Score:1)
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;
Reply to This
Parent
Re:Wrong tool for the job? (Score:2)
-sam
Re:Wrong tool for the job? (Score:1)
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;