John David Anderson wrote:
This sounds to me a like an access control issue, not a templating
system issue. If you're using your template system to manage
who-can-change what, I think there's a more fundamental issue at work.
Were you using a code-versioning system? Were you all working on the
same copy of the code?
Sparing the gorey details, let me just say it was a people problem
there, not an access issue, not a versioning issue. But it would have
been a non issue if the logic and presentation were separate via smarty
or some other means.
You can't have parse errors with Smarty?
I've seen fatal errors when people don't close their if statements. I
guess if statements mean you're introducing logic too but it's nice to
have it totally separate.
Such a setup is easy to create using plain 'ol (well architected) PHP.
Sure, but designers can't always choose their programmers either, and
might not know enough to be able to tell whether the coding is any good.
They can, however, look at a system and see whether it's been set up
with a separate template system and make decisions that way :) And
since Smarty is popular and alot of people who do 'skinning' know it ...
smarty is a logical choice. And the little console window is handy too. ;-)
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
