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.

templates 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Just did that (Score:3, Interesting)

    by ajtaylor (1283) on 2002.08.13 11:57 (#11707) Homepage Journal
    Funny you should ask as I just did something similar yesterday. Except I didn't have a unified "process" method like you do. I also lazy load the appropriate module at runtime so I don't pull in the large Template package if I'm using HTML::Template.

    But I really like your idea of a "Burner" object. This reminds me of the approach used in Bricolagem which gives you flexibility in what template system you use. I think I'm going to redo things to implement this methodology. It's a little tricky as you saw because H:T & TT use different paradigms for setting up the template & loading template data. But it's not insurmountable. Thanks for the idea!

    --
    "Perl users are the Greatful Dead fans of computer science." --slashdot comment

    • Re:Just did that (Score:3, Informative)

      by gav (2710)
      I stole the name and idea from Bricolage :)

      Loading the modules isn't an issue to me as I use PerlModule with mod_perl to preload those modules anyway. I've also been thinking about how things work and I've changed it to reuse the same TT2 object each time.

      I'll post more when I have fleshed things out even more, perhaps Template::Burner may be CPAN worthy someday...

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.