<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>qKAI project blog &#187; introductionary</title>
	<atom:link href="http://blog.qkai.org/tag/introductionary/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.qkai.org</link>
	<description>How to utilize Open Content for higher-layered applications?</description>
	<lastBuildDate>Fri, 20 Aug 2010 08:16:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>what languages qKAI is written in</title>
		<link>http://blog.qkai.org/2009/07/what-languages-qkai-is-written-in/</link>
		<comments>http://blog.qkai.org/2009/07/what-languages-qkai-is-written-in/#comments</comments>
		<pubDate>Thu, 23 Jul 2009 15:54:48 +0000</pubDate>
		<dc:creator>W-Mark Kubacki</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[introductionary]]></category>
		<category><![CDATA[qKAI]]></category>
		<category><![CDATA[statistics]]></category>

		<guid isPermaLink="false">http://blog.qkai.org/?p=102</guid>
		<description><![CDATA[Today I&#8217;ve been asked by a fellow student what languages qKAI is written in. So I launched CLOC and, before presenting you the output, I must give the remark that the actual language usage might change drastically in future. But here is the graph: 

These are &#8220;code lines&#8221; only, whatever CLOC means by that. Unit [...]]]></description>
			<content:encoded><![CDATA[<p>Today I&#8217;ve been asked by a fellow student <strong>what languages qKAI is written in</strong>. So I launched <a href="http://cloc.sourceforge.net/">CLOC</a> and, before presenting you the output, I must give the remark that <strong>the actual language usage might change drastically</strong> in future. But here is the graph: <span id="more-102"></span></p>
<p><img class="alignnone size-full wp-image-103" src="http://blog.qkai.org/wp-content/uploads/2009/07/pie-chart-r1592-language-distribution.png" alt="pie chart - r1592 language distribution" width="420" height="210" /></p>
<p>These are &#8220;code lines&#8221; only, whatever CLOC means by that. <strong>Unit tests have not been counted</strong> as well as code within comments and the documentation.</p>
<p>Since the first version (revision 863), written by Jan Hein, the distribution changed a lot. Here is another visualization, again only &#8220;code lines&#8221; count:</p>
<p><img class="alignnone size-full wp-image-105" src="http://blog.qkai.org/wp-content/uploads/2009/07/qKAI-source-code-language-history.png" alt="qKAI source code language history" width="456" height="750" /></p>
<p>In the next few days the amount of C/C++ code will double as our MySQL customizations will be extended. Most probably <strong>JSP will vanish in favour of Java</strong> and it could happen that the SQL code amount will stall where it is and a lot of Flex will be checked in.</p>
<p>We have <strong>about 12 design patterns</strong> in use, most of them have been introduced since revision 863.</p>
<p>But, as a future contributor to qKAI you don&#8217;t need to be afraid of mastering all the languages. Indeed you have the freedom to stick to two or three you know the best. That&#8217;s how everyone started and you can see where qKAI is now&#8230;</p>
<hr /><a href="http://blog.qkai.org/wp-content/uploads/2009/07/r893-cloc-output.txt">r893 cloc output</a>, <a href="http://blog.qkai.org/wp-content/uploads/2009/07/r1592-cloc-output.txt">r1592 cloc output</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.qkai.org/2009/07/what-languages-qkai-is-written-in/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

