processing / processing/libprocessing
Livecoding Mode for Python
@catilac 已经在做这个了。
开始于 2026年1月24日。
- 主要语言
- Rust
- 星标
- 69
- 派生
- 14
- 平均合并
- 15 天 22 小时
- 30 天内合并 PR
- 3
描述
Leverage bevy_ecs to watch the currently running sketch for changes and hotswap on successfully compiling edits
Edit: I'm currently working on this, but there are some architectural questions I have.
Current Approach
I've created a new bevy Asset called Sketch and spawn that object at Startup.
When I make a change to sketch.py bevy will notice. yay
The question now is how does the actual reloading mechanism work for Python? And there is a larger question of how does this mechanism work for other language frontends (Processing4/java, lua, ocaml, scheme, ruby, etc...)
For Python (w/ pyo3)
- Make a change to
sketch.py - Bevy will observe and [emit an event]
processing_pyo3crate will check if a reload is necessary- Using something like importlib.reload(), pyo3 can reload the module, and skip creating a new graphics context if it doesn't have to, and grab the new draw and setup functions.
+--------+ +------+
| Python |------->| Bevy |
+--------+ +------+
^ |
| |
+-- onChange ----+
What about other language front-ends?
I suppose some custom plugin loading could work. The Sketch Asset could be something that Python introduces, so that would allow for us to only use any of that design only for our pyo3 implementation
The other front-ends would have to build their own systems, and we could expose hot-reloading related FFI methods?
I think at the moment, I really like the idea of just having a Python related Livecoding bevy plugin. I'm still learning about bevy's ECS system, but is it possible for us to represent our "scene graph" as an intermediary that can easily map to the existing entities in bevy?
ie:
def draw():
background(220)
fill(255, 0, 100)
stroke(0)
stroke_weight(2)
rect(100, 100, 200, 150)
when I change stroke_weight, could bevy know to update, or refresh that particular entity?
or is it easier to just drop all the entities and re-run the sketch? I might be over thinking it.
For now I'm going to work towards getting python to hotreload.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。