Hello!
I wonder why is it was decided to keep up with GTK/GNOME for Pidgin3 instead of Qt? And, of course, some other Interface Questions (even stupid Questions just because I’m not smart and I’m silly) so far:
Just I’m a curious one.
Pidgin is the GTK frontend to libpurple. Previously there’s been work on a QT based frontend named Quail, but it’s never reached a releasable state. @ivanhoe has been tinkering with Quail most recently and he may have some more to add.
Also, the Pidgin/Purple team are primarily C developers not C++ developers.
What kind of themes/interface changes are you looking for? Right now we have a light/dark mode in Pidgin 3 and high constrast and accent colors should just work but right now we’re more focused on making the application work than anything else.
Historically Purple and Pidgin have always exposed their entire API to plugins, but it depends on specifically what behavior you’re looking to change.
That’s interesting…
I just thought about if someone as “old Pidgin2 User” wants to remember that Design or use it unironically… or should be that done by third-Party Plugins?
See Gaim for our gtk4 but pidgin2 like interface for purple 3.
Yeah so Quail is still purple2 and has its roots in qpe-gaim which was Gaim for Palm devices. The user interface is geared towards that and it probably doesn’t make much sense to revive it in the current form. A Qt frontend for purple3 would first require having a C++ wrapper around libpurple because GObject code and Qt code don’t mix well. I’ve somewhat recently bookmarked this Mastodon post to see if what they are doing for gstreamer can be applied to libpurple, but it’s sitting in my bookmarks with all the other things I thought might be interesting and never look at again …