[x3d-public] updates to X3DJSAIL, plus python and java versions of X3DExamples, X3DPSAIL
yottzumm at gmail.com
Wed Jun 12 15:32:36 PDT 2019
I condensed the import statements into one by returning to the X3Dautoclass.py design. Now renamed to x3dpsail.py. We can discuss the name of the package, but would like to confirm with Loren how to use variables from x3dpsail.py, either with a prepended package name, or raw. Confirming with Loren would be an important step forward.
The examples I generate might be considered exemplars, but people are free to choose what they want to do, including:
from x3dpsail import *
with no change to the x3dpsail.py file.
I am desperately trying to follow the design as laid out by Loren. I’m not disagreeing with you at all. At this point, we should be talking to Loren.
I think fully conforming to interfaces of the standard in the concrete classes would go a long way to fixing our problems. But I have no proof. I’ve left that to you as the X3DJSAIL author. I’ve said it differently, and even aggressively, and I apologize for that.
Sent from Mail for Windows 10
From: Brutzman, Donald (Don) (CIV)
Sent: Wednesday, June 12, 2019 7:22 AM
To: John Carlson
Cc: X3D Graphics public mailing list
Subject: Re: updates to X3DJSAIL, plus python and java versions of X3DExamples, X3DPSAIL
Hi John. Yesterday I belatedly noticed that, following last week's build, you recently changed the syntax of X3D .py in the default conversion output.
4. Syntax evolution. Excerpt from our exemplar scene:
X3D0 = (x3dpsail.X3D().setProfile(x3dpsail.SFString("Immersive")).setVersion(x3dpsail.SFString("3.3"))
a. Like how you were able to condense all the import statements into one, that is an important step forward. Please explain how you did that.
b. Don't like the change in the base syntax, we must remain terse/portable/pythonic. Certainly OK for developmental testing but not our final target. As listed in paragraph 3 of prior message below, our Python syntax goal remains using native types in the prior style:
X3D0 = X3D().setProfile("Immersive").setVersion(3.3)
.addMeta(meta().setContent("HelloWorld.x3d").setName("title")) // etc.
c. Towards that end, I have been studying Pyjnius and I think I know how we can get rid of those SFString/x3dpsail.SFString type wrappers so that Pyjnius employs the correct return type. Basically instead of trying to fix Pyjnius internals at this point, we might instead explicitly define interfaces for each of the set methods throughout X3D and coerce correct behavior, so that Pyjnius doesn't mistakenly return abstract node types. More work needed.
d. Am finally back from extended travels and can re-engage at a higher rate. Hoping we can pick a time later this week to discuss so that our continued co-development can proceed without collision, let's coordinate offline to find a good time.
Thanks for your continuing efforts, looks like we are getting closer. Sure would be great if we can land on a fully working X3DPSAIL implementation prior to Web3D 2019 conference next month!
On 5/27/2019 5:42 PM, Brutzman, Donald (Don) (CIV) wrote:
> X3D Java Scene Access Interface Library (X3DJSAIL) supports programmers with standards-based X3D Java interfaces and objects, all as open source.
> 1. Two useful improvements in X3DJSAIL have been applied, checked into version control and published.
> a. Have fixed long-running overzealous regular expression (regex) warnings that were getting triggered when validating large X3D models. Since regex patterns are applied against strings, pattern matching is not needed after numbers have been parsed and read into memory. Eliminating those extra warnings greatly reduced the extra messages.
> b. Exificient has been available for some time as an implementation of Efficient XML Interchange (EXI) compression standard by World World Web Consortium (W3C). Thanks t oefforts by Terry Norbraten NPS, OpenEXI is now integrated as a second implementation for EXI compression. Further work will continue on exposing options and testing across-tool compatibility as part of regular unit tests.
> c. As ever, example program HelloWorldProgram.java tests numerous features and a log of outputs is provided.
> 2. Updates have been applied and tested on X3D Examples Archives using these many scenes as a gigantic unit-testing suite.
> X3D Examples Archives
> Build logs:
> Primary example scene with multiple conversions including Java and Python source:
> 3. Development efforts continue on the X3D Python encoding using X3DJSAIL as an implementation engine. Primary tasks:
> a. Document current X3D Python implementation using Pyjnius and X3DJSAIL as X3DPSAIL, X3D Python Scene Access Interface Library (X3DPSAIL).
> b. Fix Pyjnius error which returns abstract interfaces or superclasses instead of original concrete classes. This is basis of most existing errors in the Python example builds.
> c. Move set of "import" statements from .py source to Pyjnius configuration of X3DJSAIL.
> Development efforts continue to be reflected on x3d-public mailing list.
> Having fun with X3D Java and Python! 8)
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 http://faculty.nps.edu/brutzman
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the x3d-public