SDL

1. Those will probably use SDL which has got support for wayland CSD: https://github.com/libsdl-org/SDL/pull/4068 2. Wine apps will probably have to draw the win32 decorations. Native apps can implement their own decorations or can use GTK or Qt to draw their decorations. 3. Qt does have its own CSD decorations, VLC should be able to use that. Intellij is a Java app so I'm not sure about that one but Thunderbird should use GTK decorations. The rest are Electron apps and Electron has a PR open for CSD: https://github.com/electron/electron/pull/29618 A system tray can be added to GNOME with an extension. 4. GTK is not a cross platform toolkit like Qt where it tries to draw everything with native widgets, but it is a portable toolkit meaning that you can port applications to other platforms and they will more or less look the same. I don't k

How do you mean it "can handle events"? I barely know SDL, but it does not look like it is super straightforward to integrate a socket: https://github.com/libsdl-org/SDL/blob/main/src/video/windows/SDL_windowsevents.c#… https://github.com/libsdl-org/SDL-1.2/blob/main/src/events/SDL_events.c#L403 https://github.com/SDL-mirror/SDL/blob/master/src/events/SDL_events.c#L769 Also, it seems to create a separate listener thread just to pump the messages, which I'm not sure I like. I could imagine SDL supports new event types by requiring the user to create _yet_ another thread, which waits for e.g. network events, then submits them to the SDL main event queue.

... apparently I was mistaken, this hasn't been released yet, it will be out with 2.0.18[0] [0]https://github.com/libsdl-org/SDL/milestone/2

I'm waiting for SDL to get around to merging the PR that opens up a rendering API[0], which should make writing native cross-platform GUIs a lot easier. Currently something like Dear ImGUI does work with SDL but only if you use OpenGL. I can imagine (maybe even write, if I feel like a masochist) a lightweight GUI library that uses QML like syntax in Lua. [0]https://github.com/libsdl-org/SDL/pull/4195

> The only working Wayland toolchain is tens of millions of lines of C code. What is this "Wayland toolchain" and where are its tens of millions of lines of code exactly? For comparison SDLs wayland backend implementation is like <10k lines of code: https://github.com/libsdl-org/SDL/tree/main/src/video/waylan...

Depending on how you build SDL2, your application could be entirely statically linked at build time, but you could still be using libraries dynamically loaded at runtime for other necessary system components: https://github.com/libsdl-org/SDL/blob/c59d4dcd38c382a1e9b69... This is a hard requirement if your application uses OpenGL or Vulkan, you can't really statically link those libraries at all, and you have to use dlopen/dlsym to check each individual function in order to support extensions.

Like the sibling comment points out, you can easily load your own by setting an env var: SDL_DYNAMIC_API=/my/actual/libSDL-2.0.so.0 ./MyGameThatIsStaticallyLinkedToSDL2 https://github.com/libsdl-org/SDL/blob/main/docs/README-dyna...

Ie how do you know the target's endianness? C++20 added std::endian. Otherwise you can use a macro like this one from SDL https://github.com/libsdl-org/SDL/blob/9dc97afa7190aca5bdf92...