comment on

If the web-page skeletons are written by perl-savvy developers, there is no benefit in using a templating system over perl-code. Actually, the perl-code you present could be considered some sort of a templating system in its own right.

The beauty of an MVC-system is not that it uses a templating system but makes a clear separation of concerns between the Model, Controller and View parts of the application. How each of these components is practically implemented is of far less importance and a templating system is but one possibility.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

In reply to Re: The hidden charm of Template::Toolkit (and templates generally) by CountZero
in thread The hidden charm of Template::Toolkit (and templates generally) by roman

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.


"be consistent"
	PerlMonks