[x3d-public] Fwd: Next, in Python news...

Tue Aug 24 20:41:22 PDT 2021

John, we have a lot of simple prototypes and prototypes with embedded Script nodes in the archives that have all tested OK.

If your example is that Rubiks's cube with nested prototypes, that is harder.  We believe the spec is OK but that feature is only occasionally demonstrated as working.  Any model with nested prototypes (ProtoDeclare within ProtoDeclare) can be easily refactored by putting all of the ProtoDeclare blocks first.  Similarly it makes sense to test individual ProtoInstance nodes without feeding them nested ProtoInstance fields.

Looking at existing examples is also good because they have passed through validation.  Step by step.

  *   https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples

Once again sorry I can't pursue "deep dive" excursions at this time.  Am working on (a) X3D architecture Mantis editorial issues, (b) DIS protocol implementation open-dis7-java, upgraded DIS support in Xj3D, and just tonight got X3D-Edit building despite issues with a very old laptop.  Step  by step.

From: x3d-public <x3d-public-bounces at web3d.org> On Behalf Of John Carlson
Sent: Tuesday, August 24, 2021 7:48 PM
To: Joseph D Williams <joedwil at earthlink.net>
Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: Re: [x3d-public] Fwd: Next, in Python news...

Yes, you need to '''pip install x3d'''
before running the provided script in previous message.   See link previously posted by Joe.

Thanks for confirmation of received message.

The header is the top of the file.   If you don't want to run my code, convert your own proto xml to python using X3dToPython.xslt.   I don't have a JSON converter for this test.

The main purpose is to get proper implementation of Protos in pure python.   I'm guessing it may be a wider problem with x3d.py, because when I patched Protos in my version, there were further issues.   So simply patching Protos won't fix all the issues.   A full roundtrip XML -> python -> XML needs to be done for the archive.

I've freed up some time to work on python, and I plan to start work on a test suite soon.   It would be good to get past my initial issues with the package.   I can reattempt to modify the x3d package generator, but that doesn't mean my patches will be available when I am done.    It still needs to go through official channels.

If you're fed up with stylesheets, I can offer a solution, but it's not as elegant or pythonic and uses Java.   As far as I can tell, XSLT is the declarative transformer of choice for XML.

The main thing I think needs to be done is handle cases where parameters and classes have the same case sensitive name.

If people want to contribute to x3d.py project, now's your chance.   I'm fairly sure the python binding needs to be standardized.

I know pretty much everyone has been covidized.

After spinning up python, I'll return to C++ if there's enough code separated from the standard.

John

On Tue, Aug 24, 2021 at 8:55 PM Joseph D Williams <joedwil at earthlink.net<mailto:joedwil at earthlink.net>> wrote:

# Now available: developmental python x3d.py package on PyPi for import.
#   This approach greatly simplifies Python X3D deployment and use.
#   https://pypi.org/project/x3d<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fx3d&data=04%7C01%7Cbrutzman%40nps.edu%7C72693df0fce44ec3ba3408d96772eba5%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637654565985912019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Sw68kSJJKNZaBcGFk4Up3toP5CkFxSgiUQASR49Cfos%3D&reserved=0>

The text got here as attachment
Joe

From: John Carlson<mailto:yottzumm at gmail.com>
Sent: Tuesday, August 24, 2021 3:00 PM
To: Don Brutzman<mailto:brutzman at nps.edu>; X3D Graphics public mailing list<mailto:x3d-public at web3d.org>
Subject: [x3d-public] Fwd: Next, in Python news...

Resend of non-working python code.   No rush,    I don't want anyone to be surprised.  I do want someone to confirm receipt of email.   I'm guessing things are going to spam?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210825/308a4022/attachment-0001.html>