<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: On app-specific themeable icons</title>
	<atom:link href="http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/</link>
	<description>Usability an' that</description>
	<lastBuildDate>Thu, 22 Oct 2009 17:46:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrys</title>
		<link>http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/comment-page-1/#comment-506</link>
		<dc:creator>Patrys</dc:creator>
		<pubDate>Fri, 19 Sep 2008 17:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/#comment-506</guid>
		<description>Apps that install icons to $prefix/share/icons generally adopted the idea of prefixing custom icon names with app name so it&#039;s not a bigger problem than conflicting files in $prefix/bin</description>
		<content:encoded><![CDATA[<p>Apps that install icons to $prefix/share/icons generally adopted the idea of prefixing custom icon names with app name so it&#8217;s not a bigger problem than conflicting files in $prefix/bin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: calum</title>
		<link>http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/comment-page-1/#comment-505</link>
		<dc:creator>calum</dc:creator>
		<pubDate>Fri, 19 Sep 2008 15:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/#comment-505</guid>
		<description>Er, you might think it&#039;s *not* a problem :)</description>
		<content:encoded><![CDATA[<p>Er, you might think it&#8217;s *not* a problem <img src='http://blogs.gnome.org/calum/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: calum</title>
		<link>http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/comment-page-1/#comment-504</link>
		<dc:creator>calum</dc:creator>
		<pubDate>Fri, 19 Sep 2008 15:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/#comment-504</guid>
		<description>Well, you might think it&#039;s a problem, but so far all the affected app and theme maintainers I&#039;ve mentioned it to have thought it was a bad idea...

Our theme maintainer has decided he&#039;d rather install the app-specific icons into the global theme directory for now anyway, so problem solved for this release (until there&#039;s an icon name collision, which probably won&#039;t be anytime soon...)</description>
		<content:encoded><![CDATA[<p>Well, you might think it&#8217;s a problem, but so far all the affected app and theme maintainers I&#8217;ve mentioned it to have thought it was a bad idea&#8230;</p>
<p>Our theme maintainer has decided he&#8217;d rather install the app-specific icons into the global theme directory for now anyway, so problem solved for this release (until there&#8217;s an icon name collision, which probably won&#8217;t be anytime soon&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrys</title>
		<link>http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/comment-page-1/#comment-503</link>
		<dc:creator>Patrys</dc:creator>
		<pubDate>Fri, 19 Sep 2008 15:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/calum/2008/09/19/on-app-specific-themeable-icons/#comment-503</guid>
		<description>Huh? The application either uses $prefix/share/icons or $prefix/share/$appname/$subdir. It&#039;s not something that changes over time or between bugfix releases. If a theme author wants to override the icons he just points his theme to that dir. For apps that keep icons in $prefix/share/icons it&#039;s a non-issue if a theme provides icons for an application you don&#039;t have. For $prefix/share/$appname just package the app icons into a separate package so that it can depend on the app being installed. Please keep in mind the latter is more often used when the app itself provides more than one set of icons (say one for oxygen, one for gnome and one for hicolor).</description>
		<content:encoded><![CDATA[<p>Huh? The application either uses $prefix/share/icons or $prefix/share/$appname/$subdir. It&#8217;s not something that changes over time or between bugfix releases. If a theme author wants to override the icons he just points his theme to that dir. For apps that keep icons in $prefix/share/icons it&#8217;s a non-issue if a theme provides icons for an application you don&#8217;t have. For $prefix/share/$appname just package the app icons into a separate package so that it can depend on the app being installed. Please keep in mind the latter is more often used when the app itself provides more than one set of icons (say one for oxygen, one for gnome and one for hicolor).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
