<?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: Re: Suboptimal Theming in GTK</title>
	<atom:link href="http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/</link>
	<description>My Weblog</description>
	<lastBuildDate>Tue, 24 Nov 2009 09:27:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ken</title>
		<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/comment-page-1/#comment-389</link>
		<dc:creator>ken</dc:creator>
		<pubDate>Fri, 06 Jul 2007 23:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/#comment-389</guid>
		<description>taj, could you summarize &quot;the QStyle approach&quot;?  I don&#039;t see anything in that API that&#039;s very descriptive of which way they leaned.  They have a bunch of &quot;combobox&quot; style stuff, so it looks like they haven&#039;t solved it either, but just have a really big API to handle lots of special cases (which is basically useless for custom widgets).</description>
		<content:encoded><![CDATA[<p>taj, could you summarize &#8220;the QStyle approach&#8221;?  I don&#8217;t see anything in that API that&#8217;s very descriptive of which way they leaned.  They have a bunch of &#8220;combobox&#8221; style stuff, so it looks like they haven&#8217;t solved it either, but just have a really big API to handle lots of special cases (which is basically useless for custom widgets).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Whyte</title>
		<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/comment-page-1/#comment-387</link>
		<dc:creator>Andrew Whyte</dc:creator>
		<pubDate>Fri, 06 Jul 2007 10:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/#comment-387</guid>
		<description>As in the update at the end of the article, &quot;Spatial&quot; theming certainly seems like an excellent, versatile plan for the future.

However, in the mean time, I think Gtk+ 2.x has a long life ahead of it - with many mature applications and bindings. If &quot;detail hints&quot; are a good option, good we go ahead and _define_ and document a good API (since there doesn&#039;t seem to be one currently) for these hints and include it in 2.14 or 2.16?

Many applications seem to customise TreeView widgets (inconsistently - because of the problems outlined) so they, even as a special case, would be a good priority...</description>
		<content:encoded><![CDATA[<p>As in the update at the end of the article, &#8220;Spatial&#8221; theming certainly seems like an excellent, versatile plan for the future.</p>
<p>However, in the mean time, I think Gtk+ 2.x has a long life ahead of it &#8211; with many mature applications and bindings. If &#8220;detail hints&#8221; are a good option, good we go ahead and _define_ and document a good API (since there doesn&#8217;t seem to be one currently) for these hints and include it in 2.14 or 2.16?</p>
<p>Many applications seem to customise TreeView widgets (inconsistently &#8211; because of the problems outlined) so they, even as a special case, would be a good priority&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Walters</title>
		<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/comment-page-1/#comment-386</link>
		<dc:creator>Colin Walters</dc:creator>
		<pubDate>Wed, 04 Jul 2007 16:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/#comment-386</guid>
		<description>I don&#039;t think I&#039;ve switched desktop themes in at least three years.  Not because I love my current one that much, but because I don&#039;t care how it looks as long as 

1) It&#039;s not crazy
2) It works

I agree with Jakub here - just don&#039;t use themes.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think I&#8217;ve switched desktop themes in at least three years.  Not because I love my current one that much, but because I don&#8217;t care how it looks as long as </p>
<p>1) It&#8217;s not crazy<br />
2) It works</p>
<p>I agree with Jakub here &#8211; just don&#8217;t use themes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sven</title>
		<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/comment-page-1/#comment-385</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Wed, 04 Jul 2007 15:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/#comment-385</guid>
		<description>it is already funny reading how gtk+ 3 is going to solve all problems. like quantum computing - just around the corner all the time...</description>
		<content:encoded><![CDATA[<p>it is already funny reading how gtk+ 3 is going to solve all problems. like quantum computing &#8211; just around the corner all the time&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: taj</title>
		<link>http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/comment-page-1/#comment-384</link>
		<dc:creator>taj</dc:creator>
		<pubDate>Wed, 04 Jul 2007 13:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/thos/2007/07/04/re-suboptimal-theming-in-gtk/#comment-384</guid>
		<description>What do you think of the QStyle approach: 
http://doc.trolltech.com/4.3/qstyle.html</description>
		<content:encoded><![CDATA[<p>What do you think of the QStyle approach:<br />
<a href="http://doc.trolltech.com/4.3/qstyle.html" rel="nofollow">http://doc.trolltech.com/4.3/qstyle.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
