Re: Another XLibre and/or Wayland subthread

On Tue, 28 Jul 2026 04:11:35 GMT, Charlie Gibbs wrote:

> On 2026-07-27, rbowman <[email protected]> wrote:
> 
>> On Mon, 27 Jul 2026 16:40:48 +0000, Farley Flud wrote:
>>
>>> Well, guess what.  IBM/RedHat controls the development of GTK+ and
>>> they will most like pull the plug on X11 compatibility in the future.
>>> Only Wayland (surprise, surprise) will be supported.
>>
>> Who controls Qt?  I never liked Gtk but I've been playing with it
>> lately. I still don't like it. Ridiculously long function names that
>> all start with gtk_ are a pain in the ass.
>>
>> It's ironic Gtk was developed because Qt wasn't 'free'. Be careful of
>> what you wish for.
> 
> I haven't done much GUI programming in Linux.  I'd like to port my
> Windows stuff and I've done some experimenting, but I wound up using GTK
> instead of Qt simply because only GTK has C bindings and I didn't want
> to have to rewrite everything in C++.

Usually if I'm doing GUIs on Linux I use PySide6 (PyQt6) but PyGtk isn't 
bad either. I've recently been playing with straight Gtk. VS Code is a 
little weird, at least of Ubuntu. You need to create a task.json to pick 
up the pkg-config stuff and there are some strange GTK_ environment 
variables that try to pick up nonexistent libs if you try to run the app 
from the Code terminal like 'Failed to load module "canberra-gtk-module"'. 
Unsetting them solves the problem. In a Konsole terminal only 
'GTK_MODULES=gail:atk-bridge' exists.