There are several points that we should consider before we can succesfully
compare different templating systems. Performance, Ease of use, Code
maintainability, Learning curve and the "Programming eficiency" (lines of
code you have to write to have your job done) are some (good?) examples.
A c
> That's because you're a Perl programmer. The template syntax wasn't
> designed for your tastes. It was designed for the HTML designers you will
> eventually have to work with - wether while you're actually on the project
> or when it moves into maintainance and needs design changes.
That's a
> To which HTML::Template responds: "Sure you know Perl, but does the HTML
> designer you're working with?" HTML::Template has a simple, HTML-esque
> syntax for its template files that is aimed at HTML designers.
I still think that this:
Name:
Job:
Is cleaner (we
Hi Drew,
> I'm the one who volunteered, and then I went on vacation for a 2 weeks.
> I have decided I will have a bare minimum draft done within a week. And
> then, as Matt suggested, people can just send
> suggestions/corrections/additions and the document will grow. When I
> have a draft, I'll
Hi,
I've just finished a mod_perl mini HOWTO. It will help developers to
install mod_perl and _configure_ it. Please let me know if you have any
idea to improve this document.
http://www.insite.com.br/~nferraz/projetos/mod_perl.html
See you,
Nelson
___
