You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After seeing the SDL3 migration guide I'm pretty confident I don't want to touch it. I'd be surprised if pygame smoothly migrates to it anytime soon, though the pygame-ce project is worth keeping an eye on. I think it's time to give up on SDL.
Probably should follow Kandria and use OpenGL / GLFW as a base layer. Or perhaps finally dig into Trial and see if a pygame-esque interface can be easily built on top of it? (And how about using godot as a backend instead?)
Well, for the time being, I'll probably do nothing. SDL2 isn't going anywhere.
If I do do anything, I should prioritize using fewer direct SDL calls, symbols, and data objects and instead go through the trouble of making Lisp native versions that get translated later.
e.g. an actual rect class instead of sdl-rect, whose int behavior has given me trouble before, actual Lisp render functions that can be inlined to the sdl render ones but also potentially in the future behave as just staging a render to be executed on a separate correct thread (that won't crash), and actual Lisp keyword symbols for events instead of the constants brought in from the sdl header (that are renamed now in sdl3). I get a lot of productivity by being able to tab-complete, though.
The text was updated successfully, but these errors were encountered:
After seeing the SDL3 migration guide I'm pretty confident I don't want to touch it. I'd be surprised if pygame smoothly migrates to it anytime soon, though the pygame-ce project is worth keeping an eye on. I think it's time to give up on SDL.
Probably should follow Kandria and use OpenGL / GLFW as a base layer. Or perhaps finally dig into Trial and see if a pygame-esque interface can be easily built on top of it? (And how about using godot as a backend instead?)
Well, for the time being, I'll probably do nothing. SDL2 isn't going anywhere.
If I do do anything, I should prioritize using fewer direct SDL calls, symbols, and data objects and instead go through the trouble of making Lisp native versions that get translated later.
e.g. an actual rect class instead of sdl-rect, whose int behavior has given me trouble before, actual Lisp render functions that can be inlined to the sdl render ones but also potentially in the future behave as just staging a render to be executed on a separate correct thread (that won't crash), and actual Lisp keyword symbols for events instead of the constants brought in from the sdl header (that are renamed now in sdl3). I get a lot of productivity by being able to tab-complete, though.
The text was updated successfully, but these errors were encountered: