I’m still not fully understanding you, but if you’re building something, I’d like to suggest that you don’t make it yet another abstraction layer on top of things like QT or GTK. QT and GTK are really heavy and bloated already. Adding something on top will just compound the issue.
I dunno. I personally don’t care enough about interface/look-and-feel consistency to think it warrants more computational complexity. I’m a big fan of applications that depend directly on things like XCB. I don’t know if there’s an equivalent to XCB for Wayland. I think mostly the Wayland people themselves recommend that people write client applicatons with QT or GTK or whatever, but if I found apps written directly against libwayland, I’d be inclined to prefer those over a QT or GTK alternative.
Wayland just gives you a buffer to write to, it doesn’t give you drawing primitives in the way XCB does. It’s kinda the point, and makes implementing display servers/compositors a lot simpler and easier, and most apps will be using some kind of non-XCB toolkit anyways.
So if you’re making an app you do kinda need a toolkit, but it can be a very simple and lightweight one.
most apps will be using some kind of non-XCB toolkit anyways.
Not my favorites. I’m mostly thinking of the Suckless sort of tools. dmenu, st, dwm, etc.
But yeah. If a toolkit is necessary for Wayland, then I’d love some extremely minimal options. Or better yet, exactly one minimal option so good that nobody ever feels the need for an alternative. (But that’s not going to happen. Heh.)
You can of course just write to the compositor socket directly without relying on any third-party dependency. But it will be very tedious and you will basically end up making your own toolkit (which is coincidentally kinda how GTK started).
Comments
I’m still not fully understanding you, but if you’re building something, I’d like to suggest that you don’t make it yet another abstraction layer on top of things like QT or GTK. QT and GTK are really heavy and bloated already. Adding something on top will just compound the issue.
I dunno. I personally don’t care enough about interface/look-and-feel consistency to think it warrants more computational complexity. I’m a big fan of applications that depend directly on things like XCB. I don’t know if there’s an equivalent to XCB for Wayland. I think mostly the Wayland people themselves recommend that people write client applicatons with QT or GTK or whatever, but if I found apps written directly against libwayland, I’d be inclined to prefer those over a QT or GTK alternative.
Wayland just gives you a buffer to write to, it doesn’t give you drawing primitives in the way XCB does. It’s kinda the point, and makes implementing display servers/compositors a lot simpler and easier, and most apps will be using some kind of non-XCB toolkit anyways.
So if you’re making an app you do kinda need a toolkit, but it can be a very simple and lightweight one.
Not my favorites. I’m mostly thinking of the Suckless sort of tools. dmenu, st, dwm, etc.
But yeah. If a toolkit is necessary for Wayland, then I’d love some extremely minimal options. Or better yet, exactly one minimal option so good that nobody ever feels the need for an alternative. (But that’s not going to happen. Heh.)
I’ve poked a little bit at the Go GUI toolkit “Fyne”. It appears to use OpenGL/GLFW, which is kinda neat, I think. Looks like GLFW’s dependencies are indeed quite minimal.
You can of course just write to the compositor socket directly without relying on any third-party dependency. But it will be very tedious and you will basically end up making your own toolkit (which is coincidentally kinda how GTK started).
Sign in to comment. Sign in