processing / processing/libprocessing
WASM API coverage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Description
We are missing quite a bit from the WASM api layer:
Input, 3d camera, lights, custom geometry, shaders, buffers and compute, offscreen graphics, state functions etc...
This task is a reminder to scope out that work and create issues around implementing what is missing.
A driver is #190
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing driver issue #190 and the current WASM API layer. Inventory the missing areas listed here—input, 3D camera, lights, custom geometry, shaders, buffers and compute, offscreen graphics, and state functions—and turn the scope into separate implementation issues; done means those follow-up issues are created with defined work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100