I haven't looked recently, but last time I did look (for bloxsom blogWhenever I look Dancer2 and Catalyst are the ones that come up.
templating), I did't really like the state of HTML template engines in
Perl.
I haven't looked recently, but last time I did look (for bloxsom blog templating), I did't really like the state of HTML template engines in
Perl.
In comp.lang.perl.misc, HASM <ha...@example.invalid> wrote:
Maybe it's just my poor way of asking the question, but those are not templatimg tools, even if they may include templaters. Those are "web application frameworks", kinda like getting a semi and a trailer whenI haven't looked recently, but last time I did look (for bloxsom blogWhenever I look Dancer2 and Catalyst are the ones that come up.
templating), I did't really like the state of HTML template engines in
Perl.
you want a handtruck.
You wouldn't use either to produce a static report from cronjob unless desperate or using it already. And it's not something that will play
nice with a polyglot site using Perl, PHP, and Ruby already.
So that's why I wouldn't like those.
Maybe just Template module would be good. But I'm kinda interested in
the war stories of people who have used them. "Nice on paper, but full
of subtle bugs" or "Great, but only for a limited range of tasks" or "Perfect, no complaints, would use again" or "Nice but needlessly
verbose".
Elijah
------
thinks mentioning bloxsom might have been the wrong footing
"E" == E Choroba <choroba@matfyz.cz> writes:
Template::Toolkit is good, Text::Xslate is a bit more advanced and more performant.
Template Toolkit has made me and my clients a lot of money over
the years.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 31:36:49 |
Calls: | 10,391 |
Calls today: | 2 |
Files: | 14,064 |
Messages: | 6,417,109 |