Opinion on PHP Template Engine spec revision 0.52
[email protected] (jm) Tue, 21 Mar 2000 14:03:42 +0000
| Newsgroups | php.template |
|---|---|
| Message-ID | <[email protected]> |
Hi
my background:
cgi programmer in perl, asp and PHP.
I've been using Templates on every project I've made.
Advantages: easy to maintain, easy for multilingual,
easy for team work.
The aim of the template concept:
make a html file simple enough for the designer to design
The smart stuff is in the php code.
What basically the template needs to have is:
+ variable
+ "loop" (which lacks in the perl fasttemplate and has been incorporated
in the php version)
+ speed (so maybe some kind of caching mecanism is needed)
No need for "smart" stuffs like conditional or any preprocessor like
instruction.
that can be done in php if dynamic is needed,
or with some preprocessor if the logic has to be done once.
I'd like the template engine to be kept simple,
so web designer (some who never WROTE html, just use cool tools
like dreamweaver or worse ones like xxx ) can understand and write templates.
I don't need them to write the logic. The logic is on the php side.
HTML has no logic. WebDesigners don't need to design "logic".
Basically, I don't want SMART templates,
I want a simple and standard template engine, so everyone coding php will
start to use it.
That is what my work experience showed me.
Now, may be I'm dumb and I need enlightement,
so what exactly is the advantage of SMART templates,
instead of simple templates and smart PHP code ??
Concretely I mean. Real world example I mean.
-- jm
"sorry for broken english. me no english native"