Gregory's Serverwhen do you graphics programming as a hobby you are doomed to rewrite spinning cube examples until you die. this time I'm using guile bindings to sdl3 gpu. rendered using vulkan.
 3 comments
my code so far is pretty inefficient. to optimize, I'll need to some kind of caching layer. there's a lot of per-frame calls that return pointers to pooled objects: command buffers, swapchain textures, and other things. you see the same handful of pointers repeatedly so you really *don't* want to be allocating new scheme objects for them every frame.  @dthompson Well, at least I put a spinning cube in an AR view on the G1 developer phone. Would've been around 2010 or so? I feel that's worth doing a spinning cube for. (Somewhere I may still have the video I did for that... maybe) |
in sdl2 and sdl1, you mostly deal with opaque handles to sdl objects. this makes writing bindings easy as there are very few C structs that your host language needs to fiddle with. this is *not* the case with sdl3, especially when it comes to the gpu api. by my count there are 31 structs that need to be dealt with. I've put in considerable effort towards making an api that makes this doable in guile.