Difference between revisions of "X3D Python Language Binding"
From Web3D.org
m (→Motivation) |
m (→Resources) |
||
| Line 10: | Line 10: | ||
== Resources == | == Resources == | ||
| − | + | * Python script interfaces | |
| + | ** H3D | ||
| + | ** Blender has an independent interface | ||
| + | John Carlson has produced | ||
| + | * https://github.com/coderextreme/pythonSAI | ||
== Deliverables == | == Deliverables == | ||
Revision as of 15:41, 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!
- spec relationships diagram
Resources
- Python script interfaces
- H3D
- Blender has an independent interface
John Carlson has produced
Deliverables
- prose and spec
- examples
- implementation
- game plan
