Re: I need to template this

I have one overriding reason to stick with HTML::Template, and that's the other people who are going to handle the templates after I'm done developing their application. They fall into two camps:

Programmers, who will be tempted to abuse TT's power, and end up putting business logic in the templates (I count myself in this camp: the temptation is strong)
Non-programmers; mostly graphic designers and/or end-users with administrative privileges, who don't know enough about programming to understand TT. H::T is simple enough for them to grok, but more complexity would be too overwhelming

If it were just me, I'd happily switch to TT.

Comment on Re: I need to template this

Replies are listed 'Best First'.
Re^2: I need to template this by doom (Deacon) on Apr 20, 2007 at 06:16 UTC
Hm... possibly you should consider using Mason then... one of Mason's strengths is that Mason templates tend to have the feel of HTML, which lets web-designer types feel like they know what's going on. Hypothetically a perl programmer might be inclined to slip in a lot of perl into the template, but in practice it's just as easy to put it in a perl module, and just add just enough glue code into the template to get it to use the module. Myself, I'm less familiar with Template Toolkit, but I would say if you have a choice of ways to do it, you probably want to use either Mason or Template Toolkit: those are the two competing schools at the moment (notably they both have O'Reilley books), and in effect they're defacto standards.	[reply]

Replies are listed 'Best First'.

Re^2: I need to template this
by doom (Deacon) on Apr 20, 2007 at 06:16 UTC

Myself, I'm less familiar with Template Toolkit, but I would say if you have a choice of ways to do it, you probably want to use either Mason or Template Toolkit: those are the two competing schools at the moment (notably they both have O'Reilley books), and in effect they're defacto standards.

[reply]