Am 12.04.2017 um 19:07 schrieb Matthias Clasen:
On Wed, 2017-04-12 at 18:20 +0200, Björn 'besser82' Esser wrote:
@Björn: Do you know how libyui chooses the toolkit?
Yes. Libyui performs a check on init of ui whether it's running on
a
TTY or not:
if TTY it instantly uses libyui-ncurses
else it *tries* to load - and uses the first available -
GUI-backend in the following order:
libyui-qt
libyui-gtk
libyui-ncurses
If it cannot load any backend or cannot open a TTY in case of
libyui-ncurses, it throws an error and shuts down the ui.
To throw in my 2c as gtk maintainer: I'd rather have a well-written qt
app on my desktop than something that relies on fragile toolkit
abstraction layers like this. Both gtk and qt are already abstractions.
Adding another one on top does not make things better, most of the
time...
Libyui is a well tested and since 15 years proven to work toolkit /
abstraction-layer written by SUSE, even used in SLES… It's powering
their installer and system-configuration tooling.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
