-
Notifications
You must be signed in to change notification settings - Fork 11
Milestones
List view
We want to support physical computing with an arduino like interface that would work with a different microcontrollers (esp32, RP235x, etc...)
No due dateWe have some WASM support, but we want to go as far as being able to support projects like p5.js
No due date•0/2 issues closedWe want to enable our users to easily make GUIs with our API. We have a great opportunity to leverage bevy in this regard.
No due datebevy is working to bring a more robust audio engine into their project (https://github.com/CorvusPrudens/bevy_seedling) You can play sounds, apply effects, and route audio anywhere.
No due dateWe should be able to competently use modern file formats and be able to easily be a part of creative workflows involving professional software
No due datelibprocessing needs to support [Processing](https://github.com/processing/processing4)'s visual engine at the very least. We want to get coverage for all of it https://processing.org/reference
No due date•0/1 issues closedTasks we'll want to accomplish before demoing progress at SIGGRAPH
Due by July 13, 2026We have some documentation. We would like to set a baseline with more of it. * Architecture * How to contribute * Tutorials * Examples from the community
No due date•0/9 issues closedCurrently we have been living on the edge. The bevy development branch, large gestures of feature development (rightfully) tossed in, without a testing strategy, or continuous integration. In support of [Processing](https://github.com/processing/processing4) we want to ensure that we are able to develop with confidence and able to trust more people to contribute to the project. For this milestone, we would like to: * Know when our examples break * Add visual testing * Version lock our bevy dependency * Set up continuous integration * Be in a state that inspires confidence as we bring a libprocessing powered renderer to Processing
No due date•0/7 issues closed