[X3D-Ecosystem] Reading data into x3d.py. Replace with Graalpy

[John Carlson]

AFAIK, the proven way to read X3D data into x3d.py is to convert to python.

X3DJSAIL has DOM and XML loading,  but it may be incomplete.  That doesn’t
stop me from using it.

I am going to proceed with the assumption that x3d.py will not support DOM
or XML loading.  Even though one can roll your own.  Apparently, I can’t,
at least not JSON loading.

Pyjnius continues to be a thorn in the flesh.  And node.js integrations
with java as well.

I have recently discovered how to install python packages in GraalPy
correctly, I hope.

Therefore,  I’m moving towards supporting Graalpy as an adjunct to
X3DJSAIL.  X3DJSONLD will produce Python code compatible with X3DJSAIL and
GraalPy.  Hopefully the API will not vary significantly from Pyjnius.  I
will add a second Python Serializer to X3DJSAIL.

I hope that graalpy will be supported by Blender.

I am interested in VRML to DOM solutions and may make use of vrml.g4 to
produce a new VRML parser for SAI in many languages hopefully.   A few may
get to DOM.  C++ to DOM exists as CPPON.  I will plan to offer an extension
to X3DJSAIL to load C++, if not already accomplished.

What this means is that X3DJSONLD will continue to focus on core
technologies like JavaScript (Node.js and GraalJS) and Java (GraalVM), with
Graalpy for XML parsing, if it works out.

I am hoping that recent discussions with thi-ng/geom will lead to rendering
with X3DJSAIL.

Why can’t we use XSLT to convert XSLT to something else?  That seems like a
fundamental flaw in XSLT.

Further discussions about how to break up declarative SAI apps into modules
in Java, Pascal and Clojure is welcome.

I will be looking for Deno integrations with Java.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20241014/86132a63/attachment.html>