Difference between revisions of "X3D Python Language Binding"
From Web3D.org
(→Motivation: ideas) |
m (→Motivation) |
||
| Line 3: | Line 3: | ||
Why: | Why: | ||
* multiple language bindings provide equivalent implementations of X3D Scene Access Interface (SAI) Specification, which in turn accesses the X3D Architecture Specification | * 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 | + | * 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 | * We are not afraid of programming languages that depend on whitespace | ||
Revision as of 15:37, 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
list them
Deliverables
- prose and spec
- examples
- implementation
- game plan
