Scoping exercise for p5.js support

Open
#192 0 comments 1 reaction 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, web-dev

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.

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.

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.