[x3d-public] Blender: New name for altered x3d.py—x3dv.py?

[John Carlson]

Does anyone have an issue with the Blender exporter version of x3d.py being
called x3dv.py?  That matches io_scene_x3dv, which is the newer exporter
name.

We will probably not publish a pip package at this time.  We may try to
reserve the name.

I know some people are sensitive to name collisions.

We’re particularly looking for Blender importable files to convert to .x3d
and .x3dv (or potentially any output from x3dv.py).  BVH is a good
candidate, and some animations are exportable, particularly HAnim joint
rotations right now. (ROUTEs and OrientationInterpolators).

If people are interested in other Interpolators, send or link files!

Back to work on JinLOA4 and X3DJSONLD gradle build.

Thanks,

John

On Sun, Feb 25, 2024 at 1:42 PM John Carlson <yottzumm at gmail.com> wrote:

> I got concerned that X3DUOM would be standardized in the XML encoding
> without a working x3d.py build process.  It does work on the surface, but
> fouls up around classes related to X3DVertexAttributeNode and concrete
> subclasses/subnodes.
>
> x3d.py 4.0.64.4 is okay.  Building x3d.py does not work.  If someone
> remains interested, I can post details, assuming nothing has changed.
>
> I believe this change was made to support better validation in browsers.
>
> I’m pretty sure both Andreas and I reported this when X3DUOM changed per
> Holger.
>
> The Blender exporter will proceed with an altered x3d.py.  We will attempt
> to modify the name in the Blender exporter.  That is a good suggestion, Don.
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240225/b9909169/attachment.html>