On Aug 6, 2007, at 3:16 PM, Velda Christensen wrote:
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.
My point exactly. (Though with a tool like SVN, someone else can't
blame you for code you didn't commit).
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.
My point as well - you can mess up templates with Smarty the same as
with PHP.
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. ;-)
Um, usually designers get *no* say in how an application is
architected, so that's kindof a moot point, no?
I used Smarty for years until I realized how limiting and annoying it
was. I was tired of keeping up with the Smarty *and* PHP curve,
especially since they do the exact same things. The only reason I
used Smarty after that was for some of the caching features it
offers. Aside from that, I can't see how it has any advantages over
plain PHP.
There are so many better ways to separate your application (re: MVC
frameworks, or most any framework, for that matter), I can't see why
adding another pseudo-language to the application makes things
simpler or easier to use.
-- John
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
