Re: [PHP3] Re: [PHP Template] Template Discussion
[email protected] (eschmid) Fri, 24 Mar 2000 00:21:08 +0100 (CET)
| Newsgroups | php.template |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 23 Mar 2000, Kristian Koehntopp wrote: > Thomas Jespersen wrote: > > I have not been following this "template" discussion before, but I > > just started looking at it today so perhaps I am wrong here, but: > > > > Are the templates you want to make not more or less the same as XSL? > > http://www.w3.org/Style/XSL/ > > > > I would certainly love to see a XSL Processor in PHP3. > > XSL sucks raw eggs. I have no need for sed with syntactic sugar > or sendmail style pattern matching when I can have the full > power of PHP. I want to parse the HTML/XML in a file into a > document tree, then apply transformation functions written in > PHP to that tree and dump the resulting tree to a socket. > > As soon as I have that, I may look into a method to translate > XSL into PHP code and execute them so that I may read XSL > transformations as well, but that is no issue that I think is > particularly urgent. Why learn another language with less power > when I can achieve better results by using PHP directly? XSL sucks, DSSSL rocks. Norman Walsh and James Clark are on the right way and DSSSL is the best language to do this work you have in mind. This is only true for programers and not designers. I find it a very good idea to have a basic template engine within PHP. I feel a lot better because the PHP documentation isn't written with a template engine. Designers should have the possibility to use a native template engine. If not, every good programer can build his own template engine. And that is a worst case, because any programer who have build such a engine have to write documentation on his engine or instruct and educate his designers. -Egon PS: Andrei can you provide some docs for get_class_methods(). If it is not valid (I mean if it doesn't go throu Jade) I will debug it tomorrow.