[x3d-public] Possible extensions to x3d.py (subclassing, etc)

[John Carlson]

I’m going to take the approach that x3d.py cannot be modified, and instead
use subclasses of x3d.py classes to provide order of fields as necessary
for the Blender X3DV exporter. In particular, HAnimHumanoid XML, VRML and
JSON methods will be overridden to provide containerField, field ordering,
etc.

x3d.py might take a dependency injection approach in the future, such that
one or more delegates can be replaced.  I believe dependency injection is
preferred to inheritance or monkey-patching, but X3D is pretty heavy into
inheritance, or at least interfaces.  Any dependency injection should make
any changes to output as desired.  I do not agree with totally replacing
methods, as that is a maintenance nightmare.

I apologize for all the emails over the last many days.  My mind is not as
nimble as it could be.   I do not know if I could have arrived at a
agreeable solution without all the emails.

Now you know why technical interviews terrify me.

Thanks everyone for being teddy bears.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231031/03f57abf/attachment.html>