3 ms·
GNOME doesn't have it's own theme, it uses whatever GTK uses, i.e. Adwaita by default. Gnome Shell, which is one of the few parts that does have it's own themin
by vetinari 8y ago
GNOME doesn't have it's own theme, it uses whatever GTK uses, i.e. Adwaita by default. Gnome Shell, which is one of the few parts that does have it's own theming, doesn't use GTK at all.
The reason why theming was unstable is, that it was being reimplemented. That's a thing you cannot do overnight, it takes some time. So if you want a theme that is not adwaita, you have to do exactly the same thing that the adwaita people did: update it for each release. Yes, that takes time too.
Doing things in explicitly marked unstable internals of any framework will get you the authors protecting themselves against you. In Windows, the theme authors got signed themes, in MacOS they got SIP. Yes, it is not a insurmountable problem to avoid both, that's not their purpose, but when something breaks, it is obvious who's fault it is.
GIMP is still Gtk 2 app, so it wasn't concerned with broken theming at all. They have their own work to do with the switch to GEGL.
- hackbinary 8y ago>> Gnome Shell, which is one of the few parts that does have it's own theming, doesn't use GTK at all. https://github.com/GNOME/gnome-shell/blob/1f03599d1cf888f73a33363212b99905064e2c9e/src/main.c#L16 https://github.com/GNOME/gnome-shell/blob/1f03599d1cf888f73a... Seems to me that "#include <gtk/gtk.h>" means that gnome-shell does use gtk. Or maybe I am missing some nuance of your statement.
- bonzini 8y agoIt uses it very little, and specifically doesn't use GTK for theming. Its widgets and the scene graph handling are written using Clutter, not GTK.
- yrro 8y agoGNOME Shell uses its own widget toolkit called ST. GTK+ APIs are pretty good about sebsible names, so you could grep though the source for gtk_ to see which GTK+ functionality is actually used by the shell.