AW: [PEAR-DEV] future of PEAR
| From: | Stephan Schmidt | Date: | Sun, 16 Nov 2003 18:45:27 +0000 |
| Subject: | AW: [PEAR-DEV] future of PEAR | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23679@lists.php.net to get a copy of this message | ||
Hi,
> First off, XML_Transformer is not, like your comment in braces above
> implies, a "rip-off" of something you came up with first.
> It is based on
> ideas that stem from the Roxen platform. Roxen introduced RXML (the
> Roxen Markup Language) and transformations thereof years
> before the W3C
> proposed the XML technologies everyone seems to be crazy
> about today.
patXMLRenderer was the first PHP implementation, I addressed Kris,
because he stated that he did a proof of concept, which was not
necessary any more as I already did a session on exactly the same topic
one year earlier...
> Correct me if I'm wrong, but a user of patXMLRenderer has
> "to buy" the
> whole package of patConfiguration, patTemplate and what-not and is
> bound to this framework rather than using the lightweight and
> self-sufficient XML_Transformer.
1. patXMLRenderer is an application, XML_Transformer only a class (or
set of classes). patXMLRenderer could be used by dummys, who do not know
XSLT or PHP. XML_Transformer is a tool for developers to help them
develop an application. So they are not the same, and that's not what I
wanted to say.
2. patConfiguration is not needed for patXMLRenderer.
3. patTemplate is used to transform tags without a namespace without
writing any PHP code, if you do not want to use this feature, it's
possible to switch it off. Actually it still needs patTemplate, unless
you remove some lines of code.
I wrote the comment in brackets to imply that I know what I'm talking
about, the different concepts of transforming XML, in this case PHP vs.
XSLT.
All I wanted to say is that there's no need for XML_Transformer or
similar tools, if all you want to do is transform one XML format to
another, as long as no external files or really complicated logic is
needed.
In the presentation at the PHPConf, Kris pointed out that XSLT is crap.
I don't think so. There are tasks, where XSLT is great to use, but XSLT
never was meant as a programming language, so you shouldn't complain if
there's no way to (natively) access a database.
Just my two cents.
Stephan
PS: If you answer to this mail, I think we should drop the pear-dev CC,
as it's quite off-topic.