As I am now using Sarissa instead of my own hacks for client-side transformations and given that client-side transformations is a piece of the project I recently finished for a client and am subsequently uploading it piece by piece to the production server (can never be too careful when dealing with production servers as I am sure you know!)
I decided to check to see if I had the latest build of Sarissa. As it turns out I didn't and furthermore I discovered the following in the projects description which I had never noticed before:
Sarissa is a cross-browser ECMAScript library for client side XML manipulation, including XML loading from URLs or strings, XSLT transformations, XPath queries and more. Supported: Gecko (Mozilla, Firefox etc), IE, KHTML (Konqueror, Safari).
Now, I guess that could be interpreted to mean that it supports the usage of XmlHttpRequest but given that it more than likely at least supports this I wonder how much more effort it will take to implement client-side XSLT processing via the new XMLLib osax processor (see earlier post on the matter) and AppleScript. Not being one who uses Mac I have no idea what the answer to this is but I do know some people who do use Mac quite exclusively so let me see what I can find out. More later...
TrackBack URL for this entry:
http://www.xsltblog.com/xslt-blog-mt/mt-tb.cgi/274
I think you’re confusing the scripting platforms. As far as I know, there is no easy way (that is, aside from writing an XSLT processor in JavaScript) to enable XSLT support in Safari. However, there are plans to natively support XSLT. Dave Hyatt writes about this in his blog:
http://weblogs.mozillazine.org/hyatt/archives/2004_08.html#006219
Thanks for this info Dimitri! I guess I am unsure as to the connection between AppleScript and ECMAScript as far as compatibilty is concerned. I will definitely look at this link and see what more information I can gain on the matter.
Cheers!
JavaScript is a Netscape trademark. JScript is a MS trademark.
ECMAScript is the standard.
Which is ugly and unpronounable so you can keep saying Javascript. :)