[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] non MS transform
|
Subject: Re: [xsl] non MS transform From: "M. David Peterson" <m.david.x2x2x@xxxxxxxxx> Date: Tue, 21 Dec 2004 09:59:15 -0700 |
Jeff,
As already mentioned Sarissa is a fantastic way to go for client-side
transformations. Pieter mentioned that there is no standard way as it
seems that even though the W3C does have standards set forth in
regards to DOM as far as client-side processing of XSLT there is no
set standards as these have been application specific and I doubt you
are going to be seeing ANY standards body suggesting how to tie an one
existing standard into a proprietary application like IE or Mozilla
based browsers. However, I do feel that there will be a time when the
development community simply adopts a standard that is considered as
such for no other reason that the fact that this is the way everyone
uses to stay consistent in their code base. In my experience Sarissa
is the BEST provider of a platform independent API for client-side
processing of XSLT. In looking at the main project site on SF.net >
http://sourceforge.net/projects/sarissa < there is a considerable
amount of downloads > 3166 < when you consider the fact that
a) It was only recent history (2 years or less I believe) that client
side processing was available outside of MSXML and IE.
b) For the most part "client-side is dead" was the general feeling
even until recent
c) There are still very few good examples of client-side use and as such...
d) ... as such once more good examples present themselves the bar of
expectations will be raised and we will be living in a completey
different world in regards to the "thin-client" attitude of the webs
past.
Give Sarrisa a try if you havent yet... *VERY* good implementation
!!!! (Emmanouill Batsis, the projects developer, has even implemented
the object orientation capability of Javascript using the widely
unused "prototype" keyword of the language and as such provides a
complex object based factory-styled interface and a common sense
wrapper API that allows brokering of objects allowing for extremely
complex pipelines (so to speak) to be established and could even be
extended into a message queue styled transaction server for queue
based processing of XML messages between objects. At least thats
where I hope Emmanouil takes this project as I can see that as being
quite beneficial. Its funny just how powerful Brendan Eichen made
Javascript. Really impressive for asupposed light weight scripting
language.
For what its worth, I highly recommend it.
Cheers!
<M:D/>
On Tue, 21 Dec 2004 11:26:34 -0500, Graber, Jeffrey
<jeffrey.graber@xxxxxxx> wrote:
> Howdy. I was happy as a clam with
> <html>
> <body>
> <script type="text/javascript">
> // Load XML
> var xml = new ActiveXObject("Microsoft.XMLDOM")
> xml.async = false
> xml.load("cdcatalog.xml")
>
> // Load XSL
> var xsl = new ActiveXObject("Microsoft.XMLDOM")
> xsl.async = false
> xsl.load("cdcatalog.xsl")
>
> // Transform
> document.write(xml.transformNode(xsl))
> </script>
>
> </body>
> </html>
>
> But then I was told that I had to come up with a non Microsoft approach. I thought that would be easy but my searching has not been successful.
>
> Could someone be so kind as to provide me with a "standard" solution to transforming.
>
> Thanks a million.
>
> Jeff Graber
> NG/IT/TASC
> 703 312 2289
>
>
--
:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] non MS transform, António Mota | Thread | RE: [xsl] non MS transform, Pieter Reint Siegers |
| [xsl] Cannot view XML input using X, karl | Date | Re: AW: [xsl] Translating roman num, Mukul Gandhi |
| Month |