Difference between revisions of "X3D Python Language Binding"
From Web3D.org
(→Motivation) |
(→Motivation) |
||
| Line 6: | Line 6: | ||
* We are not afraid of programming languages that depend on whitespace! | * We are not afraid of programming languages that depend on whitespace! | ||
| − | The [http://www.web3d.org/specifications/X3dSpecificationRelationships.png X3D Specification Relationships] diagram | + | The [http://www.web3d.org/specifications/X3dSpecificationRelationships.png X3D Specification Relationships] diagram shows how the various programming-language bindings and file encodings are related. |
== Resources == | == Resources == | ||
Revision as of 15:45, 20 July 2018
Motivation
Why:
- multiple language bindings provide equivalent implementations of X3D Scene Access Interface (SAI) Specification, which in turn accesses the X3D Architecture Specification
- Python is widely used, so many tools and applications might then easily create/use/produce X3D
- We are not afraid of programming languages that depend on whitespace!
The X3D Specification Relationships diagram shows how the various programming-language bindings and file encodings are related.
Resources
- Python script interfaces
- H3D
- Blender has an independent interface
John Carlson has produced
Deliverables
- prose and spec
- examples
- implementation
- game plan
