The first step into procedural animations, hopefully to achieve more natural animations, it's the "look at position": the plan is allow the players to keep their eyes on the ball or on the aim position while performing other actions.

So I just moved the #SDL3 #vala vapis to @Codeberg migrating from Github was actually pretty easy!

https://codeberg.org/edwood-grant/sdl3-vapi

I also added a new GPU rotating colored cube example. So this makes the whole thing a bit more complete .

I will probably just make the github repo either a mirror or just leave a message on top pointing the the actual repo in codeberg.

I mean it makes sense to have this project outside of big tech. I feel that, at least for me, is important.

Reviews like this remind me why I pour my heart into #gamedev. Every late night was worth it.

Muahahaha! Working on the #sdl3 #vala Vapis

So, after changing a bunch of things in the vapis, pulling my hair understanding the SDL3 GPU (is this one of the easy ones? by the gods!), and ensuring things are actually working in the vapi.

But I finally did it. I got the SDL TTF GPU test program work on vala! It needs a ton of cleanup and put in comments, but it works!!! .

It took me a while because Graphics are hard to grasp, and also real life. I'll upload it as soon as I can. #gamedev #sdl

Ambiance festive au stand PVH après que Place d'âmes de @saraschneider a gagné le prix SFFF Suisse 2024.

@ludomire @pvheditions
#sdl

Small perks of working a night shift, the quiet early mornings are a perfect time to work on some #gamedev

I've been debugging some GUI systems in preparation for a small demo.

Does #sdl have a nickname? Like sandal, or saddle, or something like that. Or are the other people in #gamedev fiddling with it taking it seriously?

GitHub - OpenRA/OpenRA: Open Source real-time strategy game engine for early Westwood games such as Command & Conquer: Red Alert written in C# using SDL and OpenGL. Runs on Windows, Linux, *BSD and Mac OS X. https://github.com/OpenRA/OpenRA #command-and-conquer #OpenSource #windows #GitHub #opengl #linux #macOS #game #sdl #C#

Woot! Managed to compile and run the first GPU sample in #sdl3 and #vala

It took me a while to fix some structs and stuff in the binding and understand better ownership of everything in vala, especially when pasing things like structs to arrays and whatnot.

But at least it works now! Not sure about leaks but oh well, I'll check later.

I'm going to rest now and later clean it all up and upload to the repo, but feel accomplished in making it work.

I'm getting clobbered trying to implement the #sdl3 #vala bindings GPU samples. I'm adapting/stealing them from TheSpyDog's SDL GPU samples github.

Not a graphics programmer and relatively new to vala, so its been interesting.

Was getting a crash and I forgot that I can debug the executables with GDB on terminal, which is nice.

Ran GDB, one look at the stack and the line of code and the solution was obvious lol. This happens because I'm a caveman and I rarely use a debugger.

A bunch of more news! From the #sdl3 #vala bindings workshop!

SDL_ttf has been implemented!

I even added a simple example that shows fallback emoji fonts!

This needs more examples though to really show how to use SDL_ttf on Vala with better feature like test engines, GPU and more.

Check it out here: https://github.com/edwood-grant/sdl3-vapi

Folks! Finally! I have published the #sdl3 #vala bindings! I'm a bit scared, I have never released bindings to the public. https://github.com/edwood-grant/sdl3-vapi

There are samples, some tests have been made, and some paltry docs can be generated.

Is this perfect? Not at all, is likely having tons of problems somewhere within many calls I haven't tested at all.

But it's usable, at least for the basic SDL3 samples. Any contributions, issues, PR, whatever your mind can think of are very welcome.

You guessed right: frame sequences. Now the sprite animations are assets bundled in the content file like the rest. No more hardcoded rectangles in my code! Yay!

https://mastodon.gamedev.place/@oldschoolpixels/114052826321433642

The writing of the whole #sdl3 Vapi for #vala is done!

Now, is it working? Well I started to port the SDL3 examples browser to find out.

There were some snags about truly learning about CCode attributes (oh, so that's why SimpleType and Compact exist! Or my favorite: I forgot to put has_type_id=false everywhere!)

But the goods news is that the render examples are all complete! I need to check more stuff and finish the current samples but it's very close to release!

Can you guess what this text file defines?

Got news! The #sdl3 #vala VAPI is going well!

Only two files left to translate: SDL_audio.h and SDL_gpu.h admittedly the newer stuff. I feel this is getting close to finally release it somewhere.

Is it perfect? No way, it's highly likely borked in places. But it's a start to begin fixing things and receive help from more capable people .

Not sure where to put this... I know Gnome has a GitLab… or maybe just on GitHub? Not sure about it.

Anyway, feeling good about this one.

#PyScript now has experimental support for #PygameCE !
Has anyone seen it in the wild?

https://docs.pyscript.net/2025.2.3/user-guide/pygame-ce/

via @pythonbytes

In my work creating the #SDL3 bindings for #vala, I noticed for example stdinc.h. It's huge! And some of it makes little sense to adapt to #vala.
I understand the goal, and it's to provide a full translation of the standard c library so you can compile SDL even in places where there is no std. Thus to bring truly full portability.
But it makes little sense in vala. It already has glibc behind. But then what would be a really necessary addition? It can be complex to do it right. 1/2
#sdl #gamedev

I got bored of hardcoding the sprite frame sequences for my #C99 #SDL #GameDev framework, so of course, instead of writing an importer for one of the various pixeling softwares out there, I came up with a text file format to write them as external assets in a more compact form. What's wrong with me?

So I managed to use callbacks on #sdl3 and #Vala, but it's weird.

You basically have to manually add CCode on your own if you want to use SDL_MAIN_USE_CALLBACKS.

It makes more sense to use SDL_MAIN_HANDLED and then invoke SDL_EnterAppMainCallbacks (enter_app_main_callbacks in vala) yourself to add your custom callbacks. Feels easier and looks less awkward.

When I release this vapi on the open, this would probably a part where help on how to make this nice would be very useful.