RFC: When does libprocessing stop being R&D
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Ruhig
- Tech-Stack
- javascript, rust, wasm
- Bereich
- computer-graphics
Rechercherichtung
Überprüfe die vorgeschlagenen Meilensteine für libprocessing-in-PDE, compute-shader und p5.js/WASM sowie die verknüpfte Arbeit an Processing4 und processing-examples-mewnala. Als abgeschlossen gilt die Aufgabe, wenn das Projekt konkrete Meilensteine vereinbart und festgelegt hat, wann libprocessing die R&D-Phase verlässt; dieses RFC identifiziert keine Implementierungsdateien oder Tests.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Rust
- Sterne
- 69
- Forks
- 14
- Ø Merge
- 15 T. 22 Std.
- Gemergte PRs (30 T.)
- 3
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus processing/libprocessing
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
processing/libprocessing#233 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
processing/libprocessing#229 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
processing/libprocessing#201 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
processing/libprocessing#194 ·
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
processing/libprocessing#146 · 1 Kommentar ·