Re: New XSLT class for PEAR

Pierre-Alain Joye wrote:

Christian Stocker wrote:

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.

Yes this makes sense.

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).

Thats what I felt when looking at it. I dont think that for dynamic content its really needed. Do you think my class should stay seperate and just define the purpose for each well enough so that developers can easily choose the one they need for the task? Or should the functionality be added to your class? Dan