WASM API coverage

Open
#193 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust, wasm
Domain
api

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.

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

Dominant language
Rust
Stars
69
Forks
14
Avg merge
15d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from processing/libprocessing

All issues in processing/libprocessing

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.