<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How to improve OpenOffice&#8217;s blood supply</title>
	<atom:link href="http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/feed/" rel="self" type="application/rss+xml" />
	<link>http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/</link>
	<description>Designing, building, selling and supporting a leading End User Database</description>
	<lastBuildDate>Sat, 22 Mar 2008 01:20:32 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tkTim</title>
		<link>http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-6</link>
		<dc:creator>tkTim</dc:creator>
		<pubDate>Fri, 23 Dec 2005 07:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-6</guid>
		<description>Bugs vs. Features 

Brown made some valid points.  I&#039;m not sure buggy is the correct term to be using in all cases.  The word wrap problem may or may not be a bug.  It could be just a feature that OOO doesn&#039;t have.  I seem to remember when MS Excel didn&#039;t do word wrapping for cell notes either.  When  the cell notes (comments) feature was first added the programmers didn&#039;t think anyone would write notes long enough  to warrant  word wrapping in a cell.  They found out  they were wrong.  For a long time Quattro Pro had a feature where you  could color the tabs in a spreadsheet.   We used MS Excel at work which didn&#039;t have this feature.  With every updated we would wish for this feature.  It took them for ever to offer this feature, seemed like years.   In fact there was a lot of features that Quattro Pro had that MS Excel didn&#039;t have for the longest  time.  Corel took over Quattro Pro and removed some of the features to make it more like MS Excel.  After complaints they added back some of the removed features.  None of these things are really bugs, it just there way of setting up the program.  

One thing that could  speed up new features for OOO would be for someone to publish a side by side comparison of features compared to MSO.  One could even rate which features should be added or updated first.</description>
		<content:encoded><![CDATA[<p>Bugs vs. Features </p>
<p>Brown made some valid points.  I&#8217;m not sure buggy is the correct term to be using in all cases.  The word wrap problem may or may not be a bug.  It could be just a feature that OOO doesn&#8217;t have.  I seem to remember when MS Excel didn&#8217;t do word wrapping for cell notes either.  When  the cell notes (comments) feature was first added the programmers didn&#8217;t think anyone would write notes long enough  to warrant  word wrapping in a cell.  They found out  they were wrong.  For a long time Quattro Pro had a feature where you  could color the tabs in a spreadsheet.   We used MS Excel at work which didn&#8217;t have this feature.  With every updated we would wish for this feature.  It took them for ever to offer this feature, seemed like years.   In fact there was a lot of features that Quattro Pro had that MS Excel didn&#8217;t have for the longest  time.  Corel took over Quattro Pro and removed some of the features to make it more like MS Excel.  After complaints they added back some of the removed features.  None of these things are really bugs, it just there way of setting up the program.  </p>
<p>One thing that could  speed up new features for OOO would be for someone to publish a side by side comparison of features compared to MSO.  One could even rate which features should be added or updated first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cardbox</title>
		<link>http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-3</link>
		<dc:creator>cardbox</dc:creator>
		<pubDate>Mon, 12 Dec 2005 15:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-3</guid>
		<description>Andrew -

Thank you for your comment. I don&#039;t know if you noticed the &lt;a href=&quot;http://linux.slashdot.org/article.pl?sid=05/12/10/0114200&amp;tid=185&amp;tid=163&quot; rel=&quot;nofollow&quot;&gt;Slashdot discussion&lt;/a&gt;. To an outsider like me, the main point that stood out was that the &quot;huge and forbidding codebase&quot; was indeed the biggest problem. Like the other huge programming projects around (not least Microsoft Office) OOo seems to be a massive lump of interconnected code, and correcting anything in it is likely to break something else. Leaving the zealots to one side, the other overall impression was that an open-source project has to be born open source, both to ensure that it has the right structure and to ensure that it has the right community backing it.</description>
		<content:encoded><![CDATA[<p>Andrew -</p>
<p>Thank you for your comment. I don&#8217;t know if you noticed the <a href="http://linux.slashdot.org/article.pl?sid=05/12/10/0114200&amp;tid=185&amp;tid=163" rel="nofollow">Slashdot discussion</a>. To an outsider like me, the main point that stood out was that the &#8220;huge and forbidding codebase&#8221; was indeed the biggest problem. Like the other huge programming projects around (not least Microsoft Office) OOo seems to be a massive lump of interconnected code, and correcting anything in it is likely to break something else. Leaving the zealots to one side, the other overall impression was that an open-source project has to be born open source, both to ensure that it has the right structure and to ensure that it has the right community backing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leslie Satenstein</title>
		<link>http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-2</link>
		<dc:creator>Leslie Satenstein</dc:creator>
		<pubDate>Sun, 11 Dec 2005 13:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-2</guid>
		<description>Andrew,
In some aspects I agree with your suppositions concerning Open Office.
However, having lived through the introduction of the PC, of the transition from DOS to Windows 1.0 and upgrade by upgrade to Windows XP, I would have to say that OpenOffice is at the Windows 2.0 level. Unlike your pessimistic belief that it will hardly improve, I see a great future for Open Office, and similar open products.

My late father can recall when the only book one could buy was hard covered. Then we progressed to the softcover pocket book, that sold at 1/100th the price. Today, we read more (for free) from the net, then elsewhere.

Due to the internet, which Microsoft preceded, that company, at it&#039;s start, had to go it alone to manage and repair bugs.  Today, with the net, the world is full of bug-killers. 

In short, the internet, and currency differences are driving the Open Software market, not to mention what satisfaction to one&#039;s ego is obtained by working on the improvement of a world class product.  

A closing question.  &quot;Why are there artists in the world who produce for joy and hobby? Do we only want those who produce for profit?  Why then do we do art for &quot;joy&quot;? &quot;  In my mind, working on a major software product is &quot;soul food&quot;. 

My bottom line is, there is no stopping Open Free software.

Leslie in Montreal.</description>
		<content:encoded><![CDATA[<p>Andrew,<br />
In some aspects I agree with your suppositions concerning Open Office.<br />
However, having lived through the introduction of the PC, of the transition from DOS to Windows 1.0 and upgrade by upgrade to Windows XP, I would have to say that OpenOffice is at the Windows 2.0 level. Unlike your pessimistic belief that it will hardly improve, I see a great future for Open Office, and similar open products.</p>
<p>My late father can recall when the only book one could buy was hard covered. Then we progressed to the softcover pocket book, that sold at 1/100th the price. Today, we read more (for free) from the net, then elsewhere.</p>
<p>Due to the internet, which Microsoft preceded, that company, at it&#8217;s start, had to go it alone to manage and repair bugs.  Today, with the net, the world is full of bug-killers. </p>
<p>In short, the internet, and currency differences are driving the Open Software market, not to mention what satisfaction to one&#8217;s ego is obtained by working on the improvement of a world class product.  </p>
<p>A closing question.  &#8220;Why are there artists in the world who produce for joy and hobby? Do we only want those who produce for profit?  Why then do we do art for &#8220;joy&#8221;? &#8221;  In my mind, working on a major software product is &#8220;soul food&#8221;. </p>
<p>My bottom line is, there is no stopping Open Free software.</p>
<p>Leslie in Montreal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew  Brown</title>
		<link>http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-1</link>
		<dc:creator>Andrew  Brown</dc:creator>
		<pubDate>Sun, 11 Dec 2005 08:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://cardbox.wordpress.com/2005/12/09/how-to-improve-openoffices-blood-supply/#comment-1</guid>
		<description></description>
		<content:encoded><![CDATA[<p>&#8221; Suppose that Andrew Brown identifies his five most irritating OpenOffice bugs and offers $1 for each of them to be solved. Suppose that thousands &#8211; eventually millions &#8211; of OpenOffice users sign up to the â€œ$1-per-bugâ€? project. Who can doubt that the oldest and most irritating bugs will get solved very soon indeed?&#8221;</p>
<p>It&#8217;s a nice idea. But it has been tried several times, and never worked. I think Mark Shuttleworth had a bug bounty on OOo for a while. There seem to me to be two problems. The first is that most of the bugs are in the bits of the program that 90% of the users don&#8217;t touch. So the pool of potential buys is much smaller than it looks. The second is that there just aren&#8217;t enough developers who know their way around this huge and forbidding codebase.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
