<?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 for Toma&#039;s blog</title>
	<atom:link href="http://www.omat.nl/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.omat.nl</link>
	<description>My Blogs.</description>
	<lastBuildDate>Sat, 21 Jan 2012 20:38:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Release Party NL by KDE Release Party NL &#171; Arie de Jonge : Linux, photography, hiking and geocaching</title>
		<link>http://www.omat.nl/2012/01/21/release-party-nl/comment-page-1/#comment-2099</link>
		<dc:creator>KDE Release Party NL &#171; Arie de Jonge : Linux, photography, hiking and geocaching</dc:creator>
		<pubDate>Sat, 21 Jan 2012 20:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=1010#comment-2099</guid>
		<description>[...] : Tom Albers via Planet KDE  Advertisement  GA_googleAddAttr(&quot;AdOpt&quot;, &quot;1&quot;); GA_googleAddAttr(&quot;Origin&quot;, &quot;other&quot;); [...]</description>
		<content:encoded><![CDATA[<p>[...] : Tom Albers via Planet KDE  Advertisement  GA_googleAddAttr(&quot;AdOpt&quot;, &quot;1&quot;); GA_googleAddAttr(&quot;Origin&quot;, &quot;other&quot;); [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE&#8217;s Infrastructure. by Links 27/9/2011:Tinycore 4.0, Android Most Popular &#124; Techrights</title>
		<link>http://www.omat.nl/2011/09/25/kdes-infrastructure/comment-page-1/#comment-2091</link>
		<dc:creator>Links 27/9/2011:Tinycore 4.0, Android Most Popular &#124; Techrights</dc:creator>
		<pubDate>Wed, 28 Sep 2011 00:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=994#comment-2091</guid>
		<description>[...] KDE’s Infrastructure. During KDE’s (one of the largest open source communities around, with about 2500 active developer accounts with direct write access to many millions of lines of code across dozens of products, and large numbers of external contributors) ongoing migration from SVN to Git, GitHub was never considered as an option because the community considers it unacceptable for an open source community to throw their weight behind a proprietary solution. [...]</description>
		<content:encoded><![CDATA[<p>[...] KDE’s Infrastructure. During KDE’s (one of the largest open source communities around, with about 2500 active developer accounts with direct write access to many millions of lines of code across dozens of products, and large numbers of external contributors) ongoing migration from SVN to Git, GitHub was never considered as an option because the community considers it unacceptable for an open source community to throw their weight behind a proprietary solution. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE&#8217;s Infrastructure. by Gonzalo Porcel</title>
		<link>http://www.omat.nl/2011/09/25/kdes-infrastructure/comment-page-1/#comment-2090</link>
		<dc:creator>Gonzalo Porcel</dc:creator>
		<pubDate>Tue, 27 Sep 2011 18:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=994#comment-2090</guid>
		<description>You guys are truly amazing. The kind of infrastructure that the KDE project enjoys would be the envy of many a-company and shows that innovation happens at every level of our lovely desktop.

Thanks.</description>
		<content:encoded><![CDATA[<p>You guys are truly amazing. The kind of infrastructure that the KDE project enjoys would be the envy of many a-company and shows that innovation happens at every level of our lovely desktop.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE&#8217;s Infrastructure. by Martin Klapetek</title>
		<link>http://www.omat.nl/2011/09/25/kdes-infrastructure/comment-page-1/#comment-2089</link>
		<dc:creator>Martin Klapetek</dc:creator>
		<pubDate>Mon, 26 Sep 2011 21:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=994#comment-2089</guid>
		<description>I&#039;m joining afiestas and saying a big thank you for all the hardwork you have done to make our coding lives easier. 

Thanks :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m joining afiestas and saying a big thank you for all the hardwork you have done to make our coding lives easier. </p>
<p>Thanks :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE&#8217;s Infrastructure. by CTown</title>
		<link>http://www.omat.nl/2011/09/25/kdes-infrastructure/comment-page-1/#comment-2085</link>
		<dc:creator>CTown</dc:creator>
		<pubDate>Sun, 25 Sep 2011 21:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=994#comment-2085</guid>
		<description>It takes a lot of people to build this desktop that we adore so much. Thanks (goes to the whole www team) for creating the infrastructure that lets so many devs, marketers, and even help-topic writers continue to build out this open and ENORMOUS platform!</description>
		<content:encoded><![CDATA[<p>It takes a lot of people to build this desktop that we adore so much. Thanks (goes to the whole www team) for creating the infrastructure that lets so many devs, marketers, and even help-topic writers continue to build out this open and ENORMOUS platform!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on KDE&#8217;s Infrastructure. by afiestas</title>
		<link>http://www.omat.nl/2011/09/25/kdes-infrastructure/comment-page-1/#comment-2084</link>
		<dc:creator>afiestas</dc:creator>
		<pubDate>Sun, 25 Sep 2011 20:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=994#comment-2084</guid>
		<description>I will never get tired of saying this, but you rock guys! I remember a few months (not even a year ago) when people was full of pessimist words for our infrastructure and with everything related to git, now we have one of the best environments to work on, really thank you.</description>
		<content:encoded><![CDATA[<p>I will never get tired of saying this, but you rock guys! I remember a few months (not even a year ago) when people was full of pessimist words for our infrastructure and with everything related to git, now we have one of the best environments to work on, really thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on [RFC] Beta: new api search tool by Eike Hein</title>
		<link>http://www.omat.nl/2011/08/28/rfc-beta-new-api-search-tool/comment-page-1/#comment-2047</link>
		<dc:creator>Eike Hein</dc:creator>
		<pubDate>Mon, 29 Aug 2011 14:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=987#comment-2047</guid>
		<description>IMHO it wouldn&#039;t make LXR useless. LXR is not for API browsing, it&#039;s for *code browsing*, and api.kde.org only knows about a fraction of our code (i.e. the code that has doxygen comments). I usually use the full-text search (http://lxr.kde.org/search) to find code examples, or the folder nav (http://lxr.kde.org/source/) when I know where I&#039;m going (since it&#039;s just serving flat files it&#039;s tons faster than either the KDE Projects or QuickGit repo viewers).

For the identifier search part, I&#039;ve actually been pondering writing a semantic replacement for LXR ...

Some time last year a Mozilla guy wrote a semantic LXR called &quot;DXR&quot; based on a gcc plugin that could satisfy searches like &quot;all classes that are subclasses of class &quot; and expand macros. I had a brief email dialog with him inquiring about the possibility to use it for KDE, but he said it wasn&#039;t ready and the project seems to have died since.

However, recently I started playing around with the Python bindings to libclang for some static analysis applications, and it seems like using libclang to produce the index needed by something like DXR would be rather trivial, and using clang would be a lot more managable than a gcc plugin from a packaging POV anyway. If I find some time I&#039;ll try to whip up a semantic LXR using it, with a Django frontend or something.</description>
		<content:encoded><![CDATA[<p>IMHO it wouldn&#8217;t make LXR useless. LXR is not for API browsing, it&#8217;s for *code browsing*, and api.kde.org only knows about a fraction of our code (i.e. the code that has doxygen comments). I usually use the full-text search (<a href="http://lxr.kde.org/search" rel="nofollow">http://lxr.kde.org/search</a>) to find code examples, or the folder nav (<a href="http://lxr.kde.org/source/" rel="nofollow">http://lxr.kde.org/source/</a>) when I know where I&#8217;m going (since it&#8217;s just serving flat files it&#8217;s tons faster than either the KDE Projects or QuickGit repo viewers).</p>
<p>For the identifier search part, I&#8217;ve actually been pondering writing a semantic replacement for LXR &#8230;</p>
<p>Some time last year a Mozilla guy wrote a semantic LXR called &#8220;DXR&#8221; based on a gcc plugin that could satisfy searches like &#8220;all classes that are subclasses of class &#8221; and expand macros. I had a brief email dialog with him inquiring about the possibility to use it for KDE, but he said it wasn&#8217;t ready and the project seems to have died since.</p>
<p>However, recently I started playing around with the Python bindings to libclang for some static analysis applications, and it seems like using libclang to produce the index needed by something like DXR would be rather trivial, and using clang would be a lot more managable than a gcc plugin from a packaging POV anyway. If I find some time I&#8217;ll try to whip up a semantic LXR using it, with a Django frontend or something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on [RFC] Beta: new api search tool by toma</title>
		<link>http://www.omat.nl/2011/08/28/rfc-beta-new-api-search-tool/comment-page-1/#comment-2046</link>
		<dc:creator>toma</dc:creator>
		<pubDate>Sun, 28 Aug 2011 17:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=987#comment-2046</guid>
		<description>Those three keywords work fine for me... with or without capitals, did you use http://api.kde.org/search ? The search in the left bar is case sensitive indeed.</description>
		<content:encoded><![CDATA[<p>Those three keywords work fine for me&#8230; with or without capitals, did you use <a href="http://api.kde.org/search" rel="nofollow">http://api.kde.org/search</a> ? The search in the left bar is case sensitive indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on [RFC] Beta: new api search tool by sebas</title>
		<link>http://www.omat.nl/2011/08/28/rfc-beta-new-api-search-tool/comment-page-1/#comment-2045</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Sun, 28 Aug 2011 17:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=987#comment-2045</guid>
		<description>Case-sensitivity ftw :)</description>
		<content:encoded><![CDATA[<p>Case-sensitivity ftw :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on [RFC] Beta: new api search tool by sebas</title>
		<link>http://www.omat.nl/2011/08/28/rfc-beta-new-api-search-tool/comment-page-1/#comment-2044</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Sun, 28 Aug 2011 17:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.omat.nl/?p=987#comment-2044</guid>
		<description>Searching for resource, kdialog and kdatetime doesn&#039;t return me any results...</description>
		<content:encoded><![CDATA[<p>Searching for resource, kdialog and kdatetime doesn&#8217;t return me any results&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

