KhronosGroup / KhronosGroup/glTF-InteractivityGraph-AuthoringTool
Documentation: Unclear which engine(s) implement which nodes
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
My understanding was that there would be a set of "core" KHR_interactivity nodes that would have to be implemented by each engine claiming KHR_interactivity support.
However, in the current implementation, e.g. the logging engine does not support animation nodes:
I saw there have been recent changes from `lifecycle/*` to `event/*`, so maybe the Logging engine implementation just hasn't been updated yet.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the logging engine's support for animation nodes with the KHR_interactivity expectations, paying attention to the reported transition from lifecycle/* to event/*. Document which engines implement which nodes and clarify whether core nodes are required for an engine claiming KHR_interactivity support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100