[x3d-public] X3dToJson.xslt vs DOM2JSONSerializer.js

[John Carlson]

New node.exe, no luck!

Trying browserify (the --node sets it up for nodejs instead of web browser).

$ browserify --node xml2all.js -o foo.js

Still waiting

$ node foo.js ../data/JoeSkinTexcoordDisplacerKick.x3d

hmmm.  Guess I'll try WASM next, if possible!

John


On Fri, May 8, 2020 at 2:35 AM John Carlson <yottzumm at gmail.com> wrote:

> Hmm.  Well, node with 32GB of memory doesn't seem to finish either.
> Looking into a new node.exe for my system.
>
> On Fri, May 8, 2020 at 2:00 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> X3dToJson.xslt wins (finishes).
>>
>> This is why we don't want to implement the XML/DOM Prototype Expander in
>> JavaScript (not that this message has anything to do with Prototype
>> Expanding, more likely my newbie JavaScript experience). I think that
>> ProtoExpanding on the server can work extremely well.
>>
>> The players:
>>
>> X3dToJson.xslt (winner)
>> $ sh don.sh ../data/JoeSkinTexcoordDisplacerKick.x3d
>>
>> DOM2JSONSerializer.js (loser)
>> $ node xml2all.js ../data/JoeSkinTexcoordDisplacerKick.x3d
>>
>> 1 Point for XSLT!
>>
>> John
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200508/88eb4363/attachment-0001.html>