[x3d-public] [x3d] X3D working group meeting planning: X3D PythonLanguage Binding

[John Carlson]

My pythonSAI assets in https://github.com/coderextreme/pythonSAI/, possibly for meeting on July 20th. Please let Jeffry and me know when we are meeting.


classes.py generates X3Dautoclass.py, The PyJNIus interface to X3DJSAIL

The next two are for the PythonSerializer.js:

fieldtypes.py generates fieldTypes.js -- a way to look up info on fields
parseom.py generates mapToMethod.js -- a way to map fields to methods

old.py generates X3Dpackage.py, the old Python SAI, to be replaced by a full SAI

allsaxon.js  -- for Saxon
config.js -- configuration
convertJSON.js -- main convert script
fieldTypes.js – a way to look up info on fields -- generated
json2py.js – calls python serializer
mapToMethod.js – a way to map fields to methods -- generated
mapToMethod2.js – supplemental map to above
moverride.js -- IDK
PythonSerializer.js – main DOM to Python serializer
runAndSend.js -- for Saxon
X3DJSONLD.js -- JSON to DOM converter

Make.sh – main build script
Profile.sh – environment
X3d2py.sh – converts X3D files to JSON, to DOM and then to Python.

make.bat – build script
profile.bat -- environment
RunSaxon.java – Java to run Saxon
X3DJSAIL.3.3.classes.jar – X3DJSAIL partial jar
X3DJSAIL.3.3.full.jar – X3DJSAIL full jar
X3dToJson.xslt, X3D to JSON stylesheet
X3dUnifiedObjectModel-3.3.xml – V3.3 object model
X3dUnifiedObjectModel-4.0.xml – V4.0 object model, currently in use
Plan (Don’s effort, with John and others assisting):

Develop X3dToPy.xslt as replacement for PythonSerializer.js, fieldTypes.js and mapToMethods*.js

Develop CreateX3DPySAIL.xslt which generates X3DPySAIL as replacement for X3DJSAIL, X3Dautoclass.py, X3DPackage.py, classes.py and old.py

Modify X3DJSAIL, X3DPySAIL to generate Python, using X3dToPy.xslt or PythonSerializer.js.
--------------------------------------------------------------------------------------------------------------------------
Others effort:

Integrate X3DPySAIL into a browser (probably 2 versions)

John’s effort: testing, Integration testing, sample testing, test scripts, verifying output from X3dToPy.xslt, CreateX3DPySAIL, python scripts etc. compare pythonSAI to X3DPySAIL.
Jeffry’s effort: Anything he wants to do.
---------------------------------------------------------------------------------------------------------------------------
Future:
Possible integration with TensorFlow, PyTorch, etc. for Recognizing and Generating 3D assets, stylizing 3D assets (similar to making 3D scenes similar to Van Gogh), etc.

I hope to build some excitement behind the python version of this.   Perhaps one of my friends will get on board X3D once we have C++ or Python versions.

John

Sent from Mail for Windows 10

From: Don Brutzman
Sent: Tuesday, July 17, 2018 9:48 AM
To: John Carlson
Cc: Valentin Christoph; X3D Graphics public mailing list; X3D Graphics Working Group
Subject: Re: [x3d] [x3d-public] X3D working group meeting planning: X3D PythonLanguage Binding

John, thanks for the continuing work on Python language binding for X3D, which we expect to someday become formalized as ISO specification 19777-6.

	X3D Graphics Standards: Specification Relationships
	http://www.web3d.org/specifications/X3dSpecificationRelationships.png

As discussed on last week's teleconference, the corresponding JSON File Encoding for X3D 19776-5 is far along thanks to implementation and specification efforts by you, Roy Walmsley and I.  Our intent is to perform a thorough review of Roy's draft specification on github after SIGGRAPH and submit New Work Item Proposal (NWIP) for specification formalization to Web3D Board of Directors and then ISO SC24 in the fall.

Suggestion: let's follow the same path of success for Python.  It will be especially good if we can have our X3D Python plan articulated prior to upcoming week-long August meetings with ISO and then at SIGGRAPH in Vancouver, we may well attract further participants.  Cooperation is helpful and productive, we can continue maturing it regularly each month of the coming year.

Request: can we review and document all of your assets during one of the next two upcoming X3D Working Group meetings?  Either this Friday 20 July or 27 July.  Please advise on your availability.

As always, thanks for your many efforts.  Have fun with X3D Python!


On 7/17/2018 5:51 AM, John Carlson wrote:
> Don Brutzman wrote:
> 
>  > No work has been proposed to X3D Working Group  yet on an X3D Python Language Binding but it keeps getting easier as we succeed with each of these.  The X3D Unified Object Model (X3DUOM) is further helping us keep all of these many variations exactly consistent. Another great professional opportunity!  Onward we go.
> 
> May I suggest that the X3D Python Language Binding be based on the Java binding?  See some python examples in:
> 
> https://github.com/coderextreme/pythonSAI/
> 
> If the Java standard is generated, perhaps the Python standard can be generated as well?
> 
> 
> I’m not sure what the best Pythonic solution is.
> 
> Perhaps it’s time to start work on an X3dToPy.xslt? We can leverage X3dToJava.xslt, and PyJNIus  for now, then move to pure python later.
> 
> What do you think?
> 
> Thanks,
> 
> John
> 


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...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180717/d0fc6297/attachment-0001.html>