SDL VS urho3d

The linked project doesn't use any ObjC files at all. SDL2 has a bunch of Cocoa files[1] so you did use Cocoa even if unknowingly.

[1] https://github.com/libsdl-org/SDL/tree/main/src/video/cocoa

Correct. It's explained here:

https://github.com/libsdl-org/SDL/pull/9345#issuecomment-201...

XWayland has special hooks into the compositors that normal wayland clients don't get.

Found about this through the release of SDL 3: https://github.com/libsdl-org/SDL/blob/main/build-scripts/SD...

https://github.com/libsdl-org/SDL/blob/main/include/SDL3/SDL_events.h

If that app ran in a 640x480 mode, memory accesses would be just as fast as the VGA applications 25 years ago, correct?

I think there's a lot more going on than that. Here's SDL's current pixel access code:

https://github.com/libsdl-org/SDL/blob/main/src/video/SDL_su...

We use the code examples throughout the article. The ellipsis characters "...." in the code were added by the author of the article. You can find the source files on the official GitHub of libsdl. In addition, each fragment has a reference to a specific area in the code. By the time this article is published, many errors will have already been fixed thanks to the issues we opened (for example, here and there). However, the links in the examples point exactly to the code you see in this article. Not only do we enjoy teasing developers but we also like making their projects a little bit better!

FetchContent_Declare(SDL2 GIT_REPOSITORY https://github.com/libsdl-org/SDL.git GIT_TAG release-2.28.3 ) FetchContent_MakeAvailable(SDL2)

It's not that difficult, I recently started learning to use graphics APIs myself. OpenGL is for linux, etc., directx for windows and vulkan for all platforms. I read through a bunch of forums yesterday and decided to go for vulkan (here is a link to the sdk) for my next small projects because it can run on all platforms. I would recommend to watch a basic tutorial series (like this one) for the graphics api itself to get an understanding of whats going on. And on top of that I use SDL2 for eventhandling and ImGui for the graphical user interface. Here is a link to a guide for setting up vulkan on your platform in case you would go for it.

SDL (which will be bumped to SDL3), straight from the authoritative https://github.com/libsdl-org/sdl

Urho3D, an open source C++ game engine.

I believe Urho3d supports MacOS (see 'about' page on the legacy website).

Urho3D

If you're literally clueless your best bet is to first start learning with an existing clean-ish engine like Urho3D implementing whatever feature/screwing-around or start with a framework like nVidia's Donut that gets you your window and basic rendering in place.

I would recommend tracking through the gist of Urho3D's batch/batchqueue stuff as it's a reasonable setup that is very intelligible (if you speak C++), it's not the greatest thing on the planet but you should be able to roughly grok it in an afternoon. Doing draw batch-pumps greatly streamlines the final drawing code.

You could try Urho3D or its newer fork rbfx.

I use an engine called rbfx which is a fork of the Urho3D engine. A lot of it is just the fact that I've been using it for over a decade, so I am comfortable with it. I'm a programmer, not really comfortable with integrated editor engines such as Unity or Godot, and the easy C++ extensibility of the engine appeals to me. Plus it's decently powerful, and well supported on a lot of platforms (I build for Windows, WebGL, and very occasionally RPi for the most part) and is open source to satisfy that stubbornly libertarian side of my character.

You might be interested in Urho3D.

If you don't mind something experimental, there is a C# version of Urho3D that is in fairly active development. There is also a C#-scriptable branch of the Urho3D fork, rbfx, located here. Both of these projects are still pretty in-the-works, but are still pretty usable.