SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
SoylentNews
GTK 4.0 Toolkit Officially Released
GTK 4.0 features new widgets and reworks to existing elements, integrated media playback support, GPU acceleration improvements like work on its new Vulkan renderer, and better macOS support are some of the leading highlights. Some other additions include data transfer improvements, overhauling shaders, GPU accelerated scrolling, custom entry widgets are easy to make, OpenGL rendering improvements beyond the Vulkan work, restoring work on HTMl5 Broadway, better Windows support, and more.
GTK 4.0 is now considered stable for applications to begin supporting it. GTK 3 will continue to be maintained for the "foreseeable future" while GTK 2 is no longer going to be supported beyond one more point release.
This discussion has been archived.
No new comments can be posted.
GTK 4.0 Toolkit Officially Released
|
Log In/Create an Account
| Top
| 18 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Cole's Law:
Thinly sliced cabbage.
(Score: 5, Interesting) by Anonymous Coward on Thursday December 17 2020, @02:12PM (2 children)
No, it is a cause to rejoice.
Incompetents and saboteurs will at last stop monkeying with the code.
Bugs that were willfully left unfixed by so-called "maintainers", could then be fixed by a community-produced patchset.
Look at GTK+1 Slackware package for an example of how it is done: https://slackware.osuosl.org/slackware64-current/source/l/gtk+/ [osuosl.org]
As to GTK+3, it will now actually get a chance, if the monkey squad will from now on confine their fun and games to the new-toy GTK+4. I, myself, have no hamsters in my ancestry to enjoy this kind of thing: https://developer.gnome.org/gtk3/stable/gtk-migrating-3-x-to-y.html [gnome.org]
(Score: 2) by leon_the_cat on Thursday December 17 2020, @08:51PM (1 child)
You know what they are so bad that i usually ended up just writing my own widgets at GDK level. That way they wouldn't explode when some 'dev' decided to completely change everything because his dog had some bone.
(Score: 0) by Anonymous Coward on Thursday December 17 2020, @09:58PM
Myself, I preferred to hack builtin widgets where possible; to keep the binary small, and to avoid breaking visual uniformity in case of theming.
Carrying around one's own widget library and just skinning them to look like GTK's counterparts is unnoticeable in a massive blob like Mozilla or LibreOffice, but would be unbecoming for something that tries to be compact. :)