Originally posted by deve
View Post
Announcement
Collapse
No announcement yet.
In Road To Qt, Audacious Switches From GTK3 Back To GTK2
Collapse
X
-
Monochrome icons in file-chooser do NOT respond to themes
Originally posted by oleid View Post/me not understanding...
What monochrome icons? Isn't that, what icon themes are for?
Client side window decorations are optional, AFAIK. Yet, they allow greater flexibility for the application designer.
Android message windows?
Furthermore, using some #ifdefs and a few build system tweaks, a gtk3 app should compile as gtk2 app.
If GTK3 continues in this direction, that work by the MATE team to port GTK2 to Wayland will become damned important in a few years, and the Cinnamon folks may have to lock and fork GTK3 just to keep their themes looking reasonable and window controls working. They've already had to fork most of GNOME, if they have to fork GTK3 and maybe even Clutter that's a lot more work for the mint team.
Comment
-
Originally posted by psychoticmeow View PostI wasn't able to read much of what you said, but the last bit about QT adoption... kind of strikes me as a good thing. I'm sick of the toolkit split.
last announcements from gtk were fixing most things that were problematic for non gnome developers. only bug i can see is that they want to wait with releasing of stable 4 for scene graph. which can be way too long
qt adoption is not necessary good thing. it was competition that created dual licensed qt after all. and i'm yet to see one decent looking qt theme
Comment
-
Gains what?
Not reading much about this porting decision but I'm wondering what benefit it could have by going Qt.
Better cross-platform support? Yes, Qt4/5 indeed has better support on Win and OS X. But how many users who may want to use cross-platform audacious over many existing ones native on these platform.
Better Linux support? Porting to Qt4 will lose Wayland support in GTK3+. Qt5, well, has not been widely adopted by Linux distributions. Besides, desktop linux is no longer the focus point of Qt world.
Comment
-
Originally posted by xeekei View PostQt should be the new standard, really. But it needs to drop the proprietary version. Become the "SDL of desktop applications".
That would actually be an interesting game development model. Albeit it is basically freemium except with more freedom.
I never looked at Qt until they changed the license model, but honestly what Digia does with their clients doesn't matter to me - I usually won't use the proprietary software produced with it anyway (I have Skype in a container for a few of my friends who like selling their souls to MS...) but we get a GPL toolkit that kicks butt with license protection from KDE.
Comment
-
Originally posted by lovenemesis View PostNot reading much about this porting decision but I'm wondering what benefit it could have by going Qt.
Better cross-platform support? Yes, Qt4/5 indeed has better support on Win and OS X. But how many users who may want to use cross-platform audacious over many existing ones native on these platform.
Better Linux support? Porting to Qt4 will lose Wayland support in GTK3+. Qt5, well, has not been widely adopted by Linux distributions. Besides, desktop linux is no longer the focus point of Qt world.
Comment
Comment