I feel the need to clarify - and disagree.

If I correctly understand your table you are saying that in all the likely scenarios templating is the way to go, unless both the logic and presentation change often, and then putting the logic in with the presentation (ala PHP) is best.

Surely with both the logic and presentation changing the best thing is to have them both seperate. As long as the interface is well defined then the two can be changed with minimal interaction.

I am currently refactoring a PHP site I wrote in 2000 into a perl site. All of the pages are becoming shorter and cleaner, even with my ruthlessly splitting them into logic and templates. This may be influencing my view on this but quite frankly there is no reason to do it the php way once you have fully understood the templating way.

Like the table though - thought provoking. Now back to that PHP...

--tidiness is the memory loss of environmental mnemonics


In reply to Re: Re: Nirvana through the templating yin yang (TT2 / CGI.pm) by EvdB
in thread Nirvana through the templating yin yang (TT2 / CGI.pm) by Aristotle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":