Re: XML Templates...

> It is a different approach. In most cases we have the templates going > back and forth between developer and designer, so having XML code might > be a tad confusing. Secondly, my personal opinion is that templates > should not have any sort of database access in them. By the time you put > DB calls, while loops, etc. you're back to reimplementing PHP. I second that. The standard in development teams is IMHo to have a task separation like Andrei describes in his document. Personally, I don't see the advantages in the Jadake approach. Whenever I see tags in what is supposed to be a programming language (be it ColdFusion, XML-QL implementations, etc.) I shudder. Then again, there are many people who love Coldfusion, so it may simply be a matter of personal preference. Having teached PHP classes, I can say though that PHP is very easy to learn, and after one two evenings people with no prior programming experience can write simple PHP applications - i think that's very comparable to learning ColdFusion. Anyway, I think that most people would be more open to an approach like Andrei describes in his document. The Jadek application may be helpful to some users and succesful as phpColdfusion :), but IMHO it should be a separate project. -Tobias