On Wed, Mar 25, 2009 at 6:12 PM, Alex Howansky <[email protected]> wrote:
>
>> A lot have been discussed, but anyway it is still difficult to decide. A
>> project is to be developed, and more persons will have to work at it. Those
>> persons will have some experience in ZF and probably also in Smarty. The
>> problem is: what are the advantages and disadvantages of using ZF Template
>> Engine vs. Smarty. How much of you use Smarty? Why do you prefer
>> Smart/Zend_View?
>
> I think the greatest advantage to using a non-PHP templating engine in your
> view layer is that you can force logical isolation between your designers
> and your programmers. This is especially important if you have untrusted or
> external designers providing input for your product. I.e., you do not want
> your designers to be able to do things like this in a view template:
>
> <?php
>
> unlink('/path/to/file');
>
> $db = new PDO('...');
> $db->query('drop table ... ');
>
> ?>
>
> Cheers,
> Alex
>
I think this is another problem it is trying to solve. With code
review, you can easily get rid off that. And as Bradley mentioned, in
many circumstances you start allowing {php} to shortcut internals.
IMHO -- if you can't trust the people you work with, you need to work
with someone else. Code review is always to your advantage.
Till
