SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The GTK3 devs strike again -- the usual fuster cluck.
Of course, not your fault Willy.
Are there any work-arounds?
For example, I like to use a pink background (#FDD9E6) as a reminder in apps that I open as root user. Some apps provide a built-in reminder, such as Thunar, but for me the colored background is more obvious.
Well, since it's not supported by the toolkit itself, there's nothing the developers can do about it.
Well, since it's not supported by the toolkit itself, there's nothing the MATE developers can do about it. The GTK3 devs are a different story.
Sorry for the snarky thread. Just an example why sometimes users get cycnical about free/libre software. You get what you paid for -- "ain't broke then reinvent the wheel until broken" seems to the motto of the GTK3 devs. Of course, "GTK3 devs" is a nice way of saying GNOME devs.
You get what you paid for -- "ain't broke then reinvent the wheel until broken" seems to the motto of the GTK3 devs. Of course, "GTK3 devs" is a nice way of saying GNOME devs.
Isn't also that the reason for why Darth Vader gone on rants about Plasma5, so many times? Apparently, this behavior is not specific only to the GNOME devs.
Last edited by ZhaoLin1457; 12-31-2018 at 12:20 PM.
Isn't also that the reason for why Darth Vader gone on rants about Plasma5, so many times? Apparently, this behavior is not specific only to the GNOME devs.
Except KDE developers aren't QT developers. They just use the QT toolkit and can only use what the QT devs put out. When the QT devs EOL QT4 for QT5, KDE developers either stick with an older unsupported version or they migrate to the newer version.
In fact GTK is a spinoff of the gimp project, the name used to stand for
Gimp ToolKit
Of course gimp and gnome are some of the many projects under the GNU umbrella.
In fact GTK is a spinoff of the gimp project, the name used to stand for
Gimp ToolKit
I actually didn't know that. Wikipedia has more info on that:
Quote:
GTK+ was originally designed and used in the GNU Image Manipulation Program (GIMP) as a replacement of the Motif toolkit; at some point Peter Mattis became disenchanted with Motif and began to write his own GUI toolkit named the GIMP toolkit and had successfully replaced Motif by the 0.60 release of GIMP.[35] Finally GTK was re-written to be object-oriented and was renamed GTK+.[36] This was first used in the 0.99 release of GIMP. GTK+ was subsequently adopted for maintenance by the GNOME Foundation, which uses it in the GNOME desktop environment.
I actually didn't know that. Wikipedia has more info on that:
BTW: the GDK library is gimp-derived too, the abbreviation stands for Gimp Drawing Kit.
See this wikipedia page en.wikipedia.org/wiki/GDK
So both these libraries are not directly related to the gnome project (although gnome does make use of them, of course).
Last edited by ehartman; 01-01-2019 at 04:53 PM.
Reason: small typing error
Except that they are mainly developed by the GNOME Project.
Gnome hijacked Gtk for their own ends, and trampled all over the wishes of other teams dependent on Gtk - Xfce and Lxde, for example. If Gtk is mainly developed by the Gnome team today it's because everyone else gave up on it. Xfce, unfortunately, are too deeply committed at this stage to Gtk, and have to submit to the Gnome diktats or die.
Last edited by Gerard Lally; 01-01-2019 at 02:05 PM.
Gnome hijacked Gtk for their own ends, and trampled all over the wishes of other teams dependent on Gtk - Xfce and Lxde, for example. If Gtk is mainly developed by the Gnome team today it's because everyone else gave up on it. Xfce, unfortunately, are too deeply committed at this stage to Gtk, and have to submit to the Gnome diktats or die.
This is a ridiculous rant. The GTK toolkit is very good, as I can see it used in MATÉ. Qt can provide more bells and whistle but is way behind GTK in some fields, like one which matters to me: accessibility to the blind users. As a result accessibility of MATÉ is second to none among Linux desktops.
As an aside, strip from your Slackware all software developed under the Gnome umbrella (list here) and see what happens
Also, not all the software they host are managed by them: for instance the Orca screen reader is developed by Joanmarie Diggs from Igalia and I can tell you with certainty that she is the only person who makes decision for Orca.
Last edited by Didier Spaier; 01-01-2019 at 03:31 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.