This Template module is just so truly wonderful!

I just had to build a generator building templates from templates, with included subtemplates and so on. It just works.

If you still roll your own template processor, just stop doing it. Use the Template Toolkit instead. It is so incredibly full-featured and easy to use.

Still stumped ...

All Hail the Template Toolkit!

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

Replies are listed 'Best First'.
Re: All Hail the Template Toolkit!
by boo_radley (Parson) on Feb 01, 2001 at 19:57 UTC
    you may be interested in the reviews section.
    Writing a (even slightly) detailed review, or examples, are much better than simply singing the hosannas for a module.
(jeffa) Re: All Hail the Template Toolkit!
by jeffa (Bishop) on Feb 01, 2001 at 19:04 UTC
    Great! Now show us what you did with it! :P

    Jeff

    L-LL-L--L-LL-L--L-LL-L--
    -R--R-RR-R--R-RR-R--R-RR
    F--F--F--F--F--F--F--F--
    (the triplet paradiddle)
    
Re: All Hail the Template Toolkit!
by sierrathedog04 (Hermit) on Feb 02, 2001 at 22:41 UTC
    My interest is in generating HTML.

    It seems to me that if one is using CGI.pm then one will probably not use Template-Toolkit very often, because their approaches are different.

    CGI.pm aims to turn HTML tags into perl functions. Thus Print p('hello') generates the appropriate paragraph tags.

    Template-toolkit, on the other hand, aims to leave markup as is and turn perl into markup. For instance, instead of saying in CGI.pm

    if (condition){ print p('hello'); }
    it appears that one would say
    [% IF condition %] <p>hello</p> [% end %]

    In cgi.pm, everything, including output, is a perl statement. In template-toolkit, nothing in the template is a perl statement, and all output appears through the template.

    In my view, combining the two approaches would be very,very confusing.

    Am I correct that those who use CGI.pm to generate a page do not also use template-toolkit at the same time to generate it?