view the rest of the comments
Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !uspolitics@lemmy.world
7) No Hit-and-Run questions.
Please don't delete your post for no apparent reason. If you plan on deleting a question later, say so in the post, or if you feel that you have a good reason to remove it, message a mod beforehand. It's not fair to the ones who took their time to answer, and it's not in the spirit of the community.
8) No Bots.
Posts or comments from bots, LLM's, AIs, Neural Networks, Transformers, or Marvin the Paranoid Android are not welcome in AskLemmy. Real humans only please.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
well imagine it as a HTML like
but designed for app GUI's on linux
but instead of being specific to QT or GTK it can work on both and still look normal
and the actual turning the language into something that GTK or QT understands, is done by a "Translator", something that turns the code onto something that your DE or Toolkit understands (like a interpreter but instead of machine code its the thing that QT or GTK understand)
and i am not looking for something like it
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).
Knowing some stuff about the APIs of Qt and GTK, it would be a mighty difficult task to do properly. Qt and GTK don't really "understand" anything, while they both have a declarative markup language (QML for Qt, GtkBuilder XML for Gtk) those are kinda just bolted-on to the imperative/object-oriented cores; that is to say, the abstractions they provide depend on a internal details and external libraries, and it would be a massive pain to design a single language around the constraints and idiosyncrasies of those two.
So, instead of translating to those existing declarative languages, you're probably better off just reimplementing your language in terms of the framework-native approach (imperative widget creation and a mainloop for GTK, OOP&signals for Qt). But this is also a lot of work to get right, even if you limit the available functionality.
An LLM can probably vomit out a prototype for this in an hour, but I feel it will not be very useful to actually make apps.
In short, you're probably better off just reading https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications and setting
QT_QPA_PLATFORMTHEME=gtk3or smth.