After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647686 - new tab Theme in gnome-tweak-tool for theme settings
new tab Theme in gnome-tweak-tool for theme settings
Status: RESOLVED DUPLICATE of bug 654864
Product: gnome-tweak-tool
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Tweak Tool maintainer(s)
GNOME Tweak Tool maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-04-13 17:47 UTC by Aleksandra Bookwar
Modified: 2011-10-22 02:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksandra Bookwar 2011-04-13 17:47:05 UTC 
There are now following different theme settings in gnome:

metacity*.xml for window manager
gtk2
gtk3
gnome-shell theme
icon theme
(and probably color scheme)

Instead of splitting theme settings in different tabs (Shell, Interface and so on)
it is better to create one tab Theme in gnome-tweak-tool, to put all these settings together.
Comment 1 Timur Kristóf 2011-04-13 17:49:51 UTC 
Agreed. This would be a nice feature.
Comment 2 Owen Taylor 2011-04-13 18:12:05 UTC 
From the perspective of the GNOME Shell team, GNOME Shell themes are both not interesting and not supportable ... we cannot commit to any stability of the CSS class names or actor hierarchy, but what GNOME Tweak tool does is up to the GNOME Tweak tool maintainers.
Comment 3 John Stowers 2011-04-14 04:57:18 UTC 
I'm supporting GS themes (e.g. from deviantart) because

1) they exist
2) they are nice
3) I can do it in such a way, via the usertheme extension, that prevents people rooting about in /usr/ and overwriting GS theme files.

If some agreement between theme authors emerges then I suspect g-t-t might version themes by the G3 version number.
Comment 4 John Stowers 2011-10-22 02:42:58 UTC 

*** This bug has been marked as a duplicate of bug 654864 ***