Rolling out shadertoy
almarklein opened this issue · 5 comments
The shadertoy utility in wgpu-py started as a minimalistic toy, and has been getting nice improvements over time, and also resulted in quite a lot of really great-looking examples.
Although @Korijn and I are excited that wgpu-py is used for this nice tool, it's not the core business of wgpy-py. And the utility has indeed been developed completely by external contributors. As the shadertoy tool becomes more mature and larger, it increasingly feels like it's time for it to "leave the nest" and be developed in its own repository.
What do you think @panxinmiao and @Vipitis?
I would happily provide a repo under the pygfx org!
I can definitely see the benefit, as there are features I am interested in having that seem out of scope (audio shaders, API support, comparing two shaders) as well as small bits to add all the functionality of the website (buffers, common, built ins).
Let me know what such a move would entail and require from me, and I will find the time.
@Vipitis you are welcome to just create a new repo and get going. But we can also help set one up into a working state (with CI and a pypi package), and you take it from there. Whatever you prefer :)
I've created https://github.com/pygfx/shadertoy and added @Vipitis with Maintainer role.
I would recommend to duplicate the wgpu-py repo and strip out the parts you don't need, then finally reorganize and clean up.
Especially the automated example testing should be very valuable for the shadertoy CI so I would advise to repurpose that.
sure, sounds great. I will take a bit of time to read through CI and GitHub actions, but starting off with what's already in this repository will be a of great utility.