comment on

My experience of introducing inexperienced programmers and Web developers to TT is that they find its dot notation easier to deal with than Perl's arrows and curly braces. The ambiguity caused by simpler syntax doesn't cause these people as many problems as the simplicity solves.

My experience with trying to explain logic to non-programmers fits yours: I had trouble explaining HTML::Template's TMPL_IF construct to one HTML designer. I think TT's syntax helps some junior programmers, though.

Your preference for using an existing language (Perl) over a mini-language (TT) fits the philosophy of Ruby's Rails project. I don't have a strong preference for either approach, but I think a separate templating system suits me better. As ever, choose the technology that suits not only the problem, but also the people who will solve it.

In reply to Re^4: Model-View-Controller: Template Toolkit vs. XSLT by tomhukins
in thread Model-View-Controller: Template Toolkit vs. XSLT by kvale

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks