RFC: When does libprocessing stop being R&D
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
- javascript, rust, wasm
- Domain
- computer-graphics
Research direction
Review the proposed libprocessing-in-PDE, compute-shader, and p5.js/WASM milestones, along with the linked Processing4 and processing-examples-mewnala work. Done means the project has agreed on concrete milestones and defined when libprocessing leaves R&D; this RFC does not identify implementation files or tests.
Written by the indexing model from the issue text.
Description
RFC
I've received a question around when libprocessing moves out of the Research and Development phase
I think this is an important question that I've failed to give a clear answer around. This is because the honest answer was always "I don't really know."
The reason this project exists at all is because Processing4 so for one thing: I would like to see that we are actually able to use libprocessing inside of the PDE.
Additionally, we are making big promises around being able to use modern rendering techniques. Something else that would prove the point is being able to do a compute shader inside of the PDE.
Last thing I want to say is that, one of the big benefits of Rust, and using Bevy is that we are able to compile to WASM. So is this is something that p5.js would be able to use?
We have shown considerable promise with mewnala and @SableRaf has been making really great progress with porting Processing examples to mewnala. Most importantly he is talented at QA and it's been helping us catch many edge cases.
What does everyone think in terms of these milestones?
- libprocessing in PDE
- compute shaders implemented in PDE
- p5.js as a possible endpoint? (Maybe this shouldn't be a blocker, but it's certainly a question that needs to be answered)
Lastly, just to remind us about the FP Texture issues beautifully documented by @tychedelia https://github.com/processing/processing4/issues/1324 which have also been a problem for some time now: https://github.com/processing/processing4/issues/724
helps push us towards making a Processing 5.0 milestone (which I will make an RFC for soon). After meeting with folks from LibreGraphicsMeeting and learning more about the Processing-java (and not p5js) community I can see much more clearly, and want to keep getting rooted in this.
- 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
- 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.
More from processing/libprocessing
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
processing/libprocessing#233 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
processing/libprocessing#229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
processing/libprocessing#201 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
processing/libprocessing#194 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/libprocessing#146 · 1 comment ·
All issues in processing/libprocessing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100