Re: Client-side cross-platform API

I wrote a very small JavaScript file which depends on JQuery for
transport and document traversal (it was already being used in our
app) which seems to navigates IE, Mozilla, Opera and Chrome very
nicely.. All the routines were spelled out quite clearly in O'Reily's
JavaScript Reference (5th edition), a book which I can't recommend
enough..  it was almost enough to make me forget 10 years of hating
Javascript.

It is not yet mature enough to share but if there was interest...

BTW: I have enjoyed this thread knowing that I am not the only one
pushing XSL in the browser.  Does anyone other than me think it's a
good idea to start a dedicated list for this domain?  The discussions
on this list tend to center on XSL 2.0 and discussions of browser
quirks and the like are generally considered off-topic.

 - michael dykman


On Tue, Jan 12, 2010 at 12:33 PM, Abel Braaksma <abel.online@xxxxxxxxx>
wrote:
> For me it's still Sarissa, even with all its quirks. Even though Sarissa
has
> been a bit quiet lately. I'd doubt whether the current new developments of
> Chrome and Safari have been followed (afaik, retrieving external resources
> with document() or xsl:import/include is still not supported): latest
> release is from May 2008.
>
> The question popped up a few times at experts-exchange and stackoverflow.
> Google has started out with AjaXSLT (http://goog-ajaxslt.sourceforge.net/),
> but isn't really mature yet. Also, Ample SDK (amplesdk.com) seems to
support
> browser agnostic XSLT processing, but I never tried that. See
> http://stackoverflow.com/questions/1052301
>
> Kind regards,
> Abel Braaksma
>
>
> Michael Kay wrote:
>>
>> What's the state-of-the-art for writing cross-browser Javascript to invoke
>> client-side XSLT transformations?
>>
>> Is it still Sarissa, or are there alternatives?
>>
>> Regards,
>>
>> Michael Kay
>> http://www.saxonica.com/
>> http://twitter.com/michaelhkay
>
>



--
 - michael dykman
 - mdykman@xxxxxxxxx

 May the Source be with you.