Re: New XSLT class for PEAR
| From: | Pierre-Alain Joye | Date: | Mon, 24 Feb 2003 16:52:38 +0000 |
| Subject: | Re: New XSLT class for PEAR | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13770@lists.php.net to get a copy of this message | ||
On Mon, 24 Feb 2003 08:42:43 -0800
Dan Kuykendall <dan@kuykendall.org> wrote:
> Christian Stocker wrote:
> > Hi
> >
> > I just looked quickly through your code...
> >
> > 1) I like the "browser supports xslt"-idea, but why aren't you
> > building the idea into the existing XSLT wrapper? 2 different
> > XSLT-Wrappers won't get my +1...
>
> I didnt spend a ton of time to understand the existing XSLT_Wrapper
> because it seemed to make it even more comlicated to use XSLT than
> just using PHP's built in XSLT. I may have missed something and do
> plan on a more detailed look. I do like the other XSLT class for the
> purpose of choosing an XSLT engine to use, but I dont really see why
> its all that important since PHP's xslt support is working pretty
> well.
It provides the common functions to set xml data, xsl sheets and returns
the result as a string or as a file. Besides that a batch mode is
available.
The main goal is to provide a common interface to create XSL
transformation with every common XSLT engine available. It is usefull to
quickly test a transformation with many engines, or to create a
publication application that does require a specific extension. Besides
that, sometimes, we need a specific engine, which provide results that
do not work with others, using it, you skip the implementation of the
specific parts.
Actually, I use it to publish documentations from OpenOffice and Word
and to test my XSL sheets with supported XSLT engines.
I keep in mind that is not a tool to use to generate dynamic contents in
an application, but more a generation tool or for a local XSLT
application (as I use it).
> > 4) Building a template system around XSLT??? mmmh, doesn't make much
> > sense to me ;)
>
> Well, I can agree, but I keep running into people who dont want to
> construct the XML.
Hmmm, they may think to use classic html template then ;-)
> Even using XML_Tree seems to throw off some people
> (which is the reason for my importVar() addition to XML_Tree).
> I will take a look at doing this later today.
Feel free to ask if needed, as it is still alpha, changes are are not a
problem.
hth
pierre