
Jon A. Cruz wrote:
Please don't just split them out.
Instead look at the existing mechanisms for named icons. GTK+ has a whole infrastructure for that already.
I know that :) However, to use the theming mechanism I have to split them off anyway, becuase as far as I can tell it doesn't support using fragments of SVG as named icons.
With regards to the HicolorTheme mechanism, it has problems: 1. We ship some icons which are present in all Gnome installations but not on Windows (e.g. the icons to rotate and flip an object). Putting those in hicolor could cause us to overwrite some files which were already there (or, actually, fail to install, because dpkg protects against overwrites). 2. Those icons would be visible to all apps and override their own app-specific icons. We don't want this. 3. It's not clear where the hicolor theme is located on Windows. With ThemableAppSpecificIcons we specify the path ourselves, so it is not a problem.
PS I'm mostly following the icon names specified in Tango's ArtLibreSet, but many of our icons don't have equivalents there, and the set seems to have duplicate icon names (e.g. boolean-union and path-union - I chose the latter).
Regards, Krzysztof Kosiński