[x3d-public] Another great idea...x3d.py

[Brutzman, Donald (Don) (CIV)]

John:

 

*	Good idea to someday align x3d.py capabilities with Blender.
*	Not a good idea to do so before Blender-X3D import, export, and design-pattern correspondences are worked out.  There is no point to facilitating production of incorrect models, indeed that can be considered harmful.

 

Relevant motto:  “ready, aim, fire – in that order” if you want to hit a target (instead of your foot).

 

So there won’t be significant additions to x3d.py or X3DJSAIL libraries regarding Blender until the Blender-X3D import/export capabilities are worked out and deployed in Blender.

 

Am confident that the individuals working on Blender-X3D capabilities will keep everyone posted when notable progress occurs.

 

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 https://faculty.nps.edu/brutzman

 

From: x3d-public <x3d-public-bounces at web3d.org> On Behalf Of John Carlson
Sent: Monday, September 25, 2023 7:49 AM
To: X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: [x3d-public] Another great idea...x3d.py

 

Instead of producing the X3D python binding with x3d.py python output, just produce working Blender bpy code.

 

Then you aren't duplicating work done by X3DJSAIL.  It also solves the Blender import issue that X3D is having...

 

Two birds with one stone?

 

Excellent!

 

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230925/beaade02/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5464 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230925/beaade02/attachment-0001.p7s>