Difference between revisions of "X3D Python Language Binding"
From Web3D.org
m (→Deliverables) |
(→Motivation: ideas) |
||
| Line 1: | Line 1: | ||
== Motivation == | == Motivation == | ||
| − | Why | + | 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 | ||
| + | * We are not afraid of programming languages that depend on whitespace | ||
| − | spec relationships diagram | + | * spec relationships diagram |
== Resources == | == Resources == | ||
Revision as of 15:36, 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
- 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
