GNOME Bugzilla – Bug 108144
Different approach to themes
Last modified: 2015-02-09 23:05:21 UTC
Hey hey, The GNOME theme interface is now collection-driven ("theme" means the collection of components, not each part) and is new using happier names for the theme components, such as "window border", "controls", etc. Perhaps it's time to change the art.gnome.org approach, so that the primary thing you download and browse through is a "GNOME Theme". Providing a method to browse the available subcomponents (ie. what art.gnome.org currently does) would also be necessary. If this happens, perhaps it would be cool to provide a "map" of theme components, so that users know which is which. For example, a couple of images notating icons from the icon theme, the window borders, the controls, etc. Not only would this make finding the themes you want easier, but it would be a good demonstration of GNOME's flexibility in this regard. Thanks! Ping me on irc if you want to chat about it. :-)
Reassigning all art.gnome.org bugs to thos@gnome.org
Unfortunatly this isn't going to happen until we actually have a "GNOME Theme" file format. There is currently no way to store a icon theme with metacity and gtk themes in the same archive. I have created bug 325300 to try and resolve this problem.
There will be "theme collections" feature in ago3. "AGO3 will support simple themes, such as Gtk+ themes, Icon themes, Metacity themes, Splash screens, Wallpapers, Cursor themes and Sounds and also complete themes (gtk+, mcity, iconset in one package). We will support official Gnome application themes only."
art.gnome.org is not under development anymore. Closing this report as OBSOLETE.