[x3d-public] X3DOM ProtoDeclares that work.

[John Carlson]

https://coderextreme.net/X3DJSONLD/src/main/html/proto.html

select one of the X3D files that start with ./data/

Like:

./data/bubs.x3d
./data/rubik.x3d
./data/x3domflowers.x3d
./data/X3dHeaderPrototypeSyntaxExamples.x3d

If you run my app.js server (requires SSL keys) locally, then you can test
more of the x3d resources  examples by checking out the X3D sourceforge
project to /c/x3d-code/www.web3d.org/...

Start the server with

node app.js

then go to https://localhost:3000/src/main/html/proto.html

then select some of the ./www.web3d.org/... files.

Note that this does proto expansion on JSON, so first i translate from XML
to JSON, then do the proto expansion, then convert back to XML.

You may optionally turn off scripting and proto expansion, if you want to
see differences.

There need to be some effort to make this work in all cases.

1.  Don't hog graphics contexts.
2.  Fix up Scripting on X3DOM.   This may be possible with Scripts.js (not
recommended).  Primarily, I recommend fixing routing to/from scripts in
X3DOM. That may mean approaching the w3c to allow fields in a script nodes.
3.  Make sure PROTOs are working in all cases.  Please file issues against
X3DJSONLD.   I already know there are many unwritten issues.
https://github.com/coderextreme/X3DJSONLD/issues

Note that app.js does not work on a production machine purposefully.  You
may want to rewrite app.js in python. Whatever floats your boat, changes
are welcome.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200501/320caf68/attachment.html>