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 hacking code and hacking templates. For a job like that, TT makes a heck of a lot more sense. Hell, from that perspective even Mason starts making sense.
So, in closing, use the right tool for the job. Then you won't be tempted to slandor that poor wrench you're trying to use as a drill.
-sam
PS: All that said, I've never had an HTML generation problem I couldn't solve with HTML::Template. If you post a full description on PerlMonks you'll be sure to get a solution.
Reply to This
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 ver
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
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;