[x3d-public] Don, XSLT protoexpander?

John Carlson yottzumm at gmail.com
Wed May 6 21:57:18 PDT 2020


Yes, one would do the XSL transform in javascript, see:

https://www.w3schools.com/xml/xsl_client.asp

John

On Wed, May 6, 2020 at 11:53 PM John Carlson <yottzumm at gmail.com> wrote:

> Can we convert XSLT files to JavaScript?   That's Saxon-JS, right?  I am a
> bit worried about Saxon-CE.  Browser-native XSLT 1.0 processing might be
> feasible? That would be best.  Then there would be less code to download?
> It would be worth seeing if there's a good product for XSLT 2.0 in the
> browser.
> What features of XSLT 2.0 are we using in the various stylesheets?
>
> We are looking at a total remake for XML/DOM, I think, not sure.  I am
> fairly sure the code deserves re-engineering.
>
> Will look.
>
> John
>
> On Wed, May 6, 2020 at 11:41 PM Don Brutzman <brutzman at nps.edu> wrote:
>
>> If X3DOM is written in Javascript then I recommend writing the
>> ProtoExpander in Javascript.  Then it will be directly compatible and
>> maintainable.
>>
>> On 5/6/2020 9:32 PM, John Carlson wrote:
>> > Don, are we on track for an XML/XSLT ProtoExpander for integration into
>> X3DOM?  Is it on the wish list?
>> >
>> > Thanks,
>> >
>> > John
>>
>> all the best, Don
>> --
>> Don Brutzman  Naval Postgraduate School, Code USW/Br
>> brutzman at nps.edu
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
>>  +1.831.656.2149
>> X3D graphics, virtual worlds, navy robotics
>> http://faculty.nps.edu/brutzman
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200506/21ff773f/attachment-0001.html>


More information about the x3d-public mailing list