[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)

Subject: Re: [xsl] [ANN] Saxon-CE 1.0 (XSLT 2.0 on the browser)
From: Philip Fearon <pgfearo@xxxxxxxxxxxxxx>
Date: Thu, 14 Jun 2012 22:30:34 +0100

Just to expand on Michael's comment on hooks and interfaces: Saxon-CE
currently has a capability to make function calls to an app hosting a
web browser via the window.external object. There's just one function
supported, saxonErrorHandler - for sending error and diagnostics
messages (like xsl:message or fn:trace() output) to the host

To initiate the 'bridge' connection (to check the function exists
within the external object), Saxon-CE's first call uses a special INIT
logLevel - so one simple solution would be for the host app to send a
license key in response to this first call. I'm getting into solution
space too early here, but the main thing is that this is certainly
feasible from a technical standpoint.

Phil Fearon


On Thu, Jun 14, 2012 at 10:02 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>>Is there an option to package Saxon CE (local machine) only with a
>> particular app, so that the app users will not be required to obtain and
>> re-register a license?
> Not at the moment. We've always known such requirements would come up, but
> we put them to one side to worry about once we had the basic end-user
> product out. There's a whole load of ways people are going to want to
> configure this technology - Phil has been looking at the way Windows 8 uses
> HTML5 and Javascript for non-web applications, for example - and it will
> take us time to work out what hooks and interfaces we need to exploit all
> the opportunities, as well as the commercial offerings we need to put in
> place.
> Michael Kay
> Saxonica

Current Thread