processing / processing/libprocessing
Scoping exercise for p5.js support
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Description
@limzykenneth did a proof of concept of a p5.js using libprocessing as a renderer in #157
I'm making this issue as a reminder for us to have a discussion around this, and how libprocessing can support p5.js needs as we build out more WASM support.
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
Review the proof of concept referenced in issue #157 and the planned WASM support context first. Use the discussion to define the scope of p5.js support and record an agreed implementation target; the issue is done when that scope is decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100