3 ms·
This is Gnome/GTK, not cross-platform like I would have expected. A Linux-first approach. I’m happy that this is the world we’re in now but expect it still to b
by pitched 1mo ago
This is Gnome/GTK, not cross-platform like I would have expected. A Linux-first approach. I’m happy that this is the world we’re in now but expect it still to be royal pain to get a build running on Windows. Huge congrats to everyone involved if not!
- ethin 1mo agoYou also won't have accessibility on Windows either unless you can somehow get it to enable accesskit integration. (I really don't get the open source norm that something like accessibility should be opt-in, particularly with UI toolkits and the like, but eh.)
- red_admiral 1mo agoHow many proper cross-platform approaches are there these days? Just about every one I've seen is "grab the native platform's canvas, draw your own".
- josephg 1mo ago- Grab the native canvas, draw your own UI - Electron and friends (web toolkits, tauri, etc) - Or my favorite: Just have a UI library which wraps all the native UI toolkits on each platform. Eg: https://daybrite.dev/ https://daybrite.dev/
- flossly 1mo agoDoesn't Qt wrap native UI toolkits? It looks very native...
- roblabla 1mo agoAFAIK, the OS-specific Qt themes don't wrap the native widgets, it reimplements them. They are rather thorough though, making sure their OS-specific theme matches the look and behavior of the native OS, which makes it one of the best framework to do something that feels close to native.
- flossly 1mo agook. did not know that.
- red_admiral 1mo agoNo, it's just the most accurate re-implementation that I know of at least for Windows. You can sometimes tell the difference because the QT emulated widget can do things that the native widget can't.