Re: [PHP3] Re: [PHP Template] Re: [PHP3] PHP Template Engine spec revision 0.52

> In my opinion, that's bad.  It has nothing to do with the language Andrei
> suggested.  He may argue that it's better, I may argue that it's not.  It
> doesn't matter.  The point is that PHP should not feature two
> completely different syntaxes to do the same thing.  It's bad for the
> users.

From that perspective I can see the adverse effects imposed upon php
developers.

I must apologise, I havent read the whole thread, and the mention of
templates and PHP got me a little excited.

I guess another way to approach the subject is to look at sgml.  Please
excuse my lack of knowledge on the subject, however, since I've only just
started reading up on it.

The difficulty lies I feel when approaching the subject of designers /
content writers is deciding whether a designer really needs logic or
not.  Surely a designer needs to design, and leave the logic/scripting to
the programmer?  This highlights sgml/xml.  The only problem there is that
for this sort of system to work effectively, the DTD would require
modifying for each individual site (to a certain degree).  While this
means a little extra work at the start of the project, it does mean that
custom tags can be defined that would 'suck in' the required PHP
functionality.

I guess what I'm trying to say is that PHP doesnt actually need to be
modified in order to provide a template system.  A 3rd party solution will
do the job just as well; just not in realtime.  If logic IS required at
design level, then surely tags can be defined in a similar way to
CF?  i.e. <if> <endif> etc. (just an example) that the SGML parser would
interpet appropriately.

Unfortunately with the tight integration that scripting languages need
with the content, I dont think we'll ever come up with an 'ideal'
solution.

I do see what you're saying.  My mind was changed.

Cliff Rowley

- while (!asleep) { code(); }