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

Which templating system do you use?

Displaying poll results.
Template Toolkit
  35% 70 votes
HTML::Template
  25% 51 votes
Text::Template
  3% 7 votes
HTML::Mason
  11% 22 votes
Another on the CPAN
  5% 11 votes
MINE!
  19% 39 votes
200 total votes.
[ Voting Booth | Other Polls | Back Home ]
  • Don't complain about lack of options. You've got to pick a few when you do multiple choice. Those are the breaks.
  • Feel free to suggest poll ideas if you're feeling creative. I'd strongly suggest reading the past polls first.
  • This whole thing is wildly inaccurate. Rounding errors, ballot stuffers, dynamic IPs, firewalls. If you're using these numbers to do anything important, you're insane.
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.
  • By far the best template system available for Perl. You can pass hash references from your script to the template, and iterate through arrays or hashes, etc. also has macros, which I have yet to use.
  • I used HTML::Template for two years and greatly enjoyed the switch from that to Template::Toolkit. T::T makes templating dead simple, plus powerful features are available when you dig a little deeper.

    Template::Toolkit makes it blindingly easy to format data structures -- wanna mark up that RSS feed? Just pass an XML::RSS object to the process() method and instantly do things like [% FOREACH item = items %]<li>[% item.title %]</li>[% END %] -- check out "How to Avoid Writing Code" [perl.com]
    --
    qw(Ian Langworth)
  • does anyone use XSLT anymore? I think it's a great combo with perl