Well, some parts of wine (like winecfg and the explorer) have a gui, and if you start a windows software that has a gui, you will see this gui too. So from a user POV I wouldn't call wine GUI-less, because there is something like a GUI.
From a technical POV that's a bit different, because if you look at the dependencies, you'll see that wine doesn't depend on a GUI-toolkit like QT or GTK. And since wine reimplements the API provided by the windows system and its libraries including the ones responsible for handling user input (like mouse clicks and key presses) and graphical output (like drawing windows), which work on a pretty low level, it makes a lot of sense to just use low level linux apis (like x window and glu) instead a user level toolkit that might be able to achieve the same things, but would probably have more overhead (because of the abstraction) and probably also some limitations. And besides that, you would most likely not be able to use a lot of stuff included in the toolkit, because it doesn't really help, when working low level.
Opako
wrote:
↑
Mon Nov 23, 2020 11:41 am
Thank you. Do you trying to say, that the Graphical User Interface of wine is programmed in "C" from scratch?
In a sense yes. Wine creates GUI components by calliing directly on the Linux kernel API than by using toolkits like QT or GTK.
