<?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: KOffice needs you, and we need KOffice!</title>
	<atom:link href="http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/feed/" rel="self" type="application/rss+xml" />
	<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/</link>
	<description>Free Software Developer and Enthusiast</description>
	<lastBuildDate>Mon, 06 Sep 2010 16:28:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Pubudu Kodikara</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-10552</link>
		<dc:creator>Pubudu Kodikara</dc:creator>
		<pubDate>Sun, 29 Nov 2009 04:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-10552</guid>
		<description>K Ofiice had helped us a lot, so its time for payback!</description>
		<content:encoded><![CDATA[<p>K Ofiice had helped us a lot, so its time for payback!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the_madman</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8414</link>
		<dc:creator>the_madman</dc:creator>
		<pubDate>Tue, 11 Aug 2009 12:51:04 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8414</guid>
		<description>I&#039;ve always looked at the KDE re-write when it comes to innovation and have used it as my benchmark consistently: KDE and KOffice can get away with new and intuitive concepts because they&#039;ve written the applications from the ground up, for TODAY&#039;s needs and not the needs of users several years ago. Dumping more and more code onto (koffice/kde/whatever) would have just made it large, slow, harder to fix and harder to innovate. I&#039;m glad someone recognized this at all, and now KDE is my desktop of choice because of it.

I&#039;d also like to move away from OOo post-haste...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always looked at the KDE re-write when it comes to innovation and have used it as my benchmark consistently: KDE and KOffice can get away with new and intuitive concepts because they&#8217;ve written the applications from the ground up, for TODAY&#8217;s needs and not the needs of users several years ago. Dumping more and more code onto (koffice/kde/whatever) would have just made it large, slow, harder to fix and harder to innovate. I&#8217;m glad someone recognized this at all, and now KDE is my desktop of choice because of it.</p>
<p>I&#8217;d also like to move away from OOo post-haste&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Purple-Bobby</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8393</link>
		<dc:creator>Purple-Bobby</dc:creator>
		<pubDate>Wed, 05 Aug 2009 19:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8393</guid>
		<description>The problem MS have, is they wish to keep the 1500 functions that need a tool bar button - at 16 by 16 pixels that is 800 pixels by 480, rather than drop the little used functions. They also have internal clients (in marketing) that want the UI to be not too different than before, hence buttons at the top, the same type of functions in Word and Excel are described and used differently.
The design is back-to-front: they have an application with 1500+ defined functions, and they slap an UI on it.

Computers are getting more powerful, but proportionally less of that power is helping the user get the job done compared to engaging the user in needless work and entertainment.

What Ooo seem to have done wrong, was ask programmers how to fix their UI. If you view the presentation on the development of the ribbon interface, then it seems to make perfect sense (and it is right for what MS are trying to do), but it misses the point - making a better word-processor than Word, by making it faster for a user to complete a document, by using the computers power to reduce the amount UI interaction needed to complete the job - it is not about finding the button to do the function, it is making that function unnecessary.</description>
		<content:encoded><![CDATA[<p>The problem MS have, is they wish to keep the 1500 functions that need a tool bar button &#8211; at 16 by 16 pixels that is 800 pixels by 480, rather than drop the little used functions. They also have internal clients (in marketing) that want the UI to be not too different than before, hence buttons at the top, the same type of functions in Word and Excel are described and used differently.<br />
The design is back-to-front: they have an application with 1500+ defined functions, and they slap an UI on it.</p>
<p>Computers are getting more powerful, but proportionally less of that power is helping the user get the job done compared to engaging the user in needless work and entertainment.</p>
<p>What Ooo seem to have done wrong, was ask programmers how to fix their UI. If you view the presentation on the development of the ribbon interface, then it seems to make perfect sense (and it is right for what MS are trying to do), but it misses the point &#8211; making a better word-processor than Word, by making it faster for a user to complete a document, by using the computers power to reduce the amount UI interaction needed to complete the job &#8211; it is not about finding the button to do the function, it is making that function unnecessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael "I don't hate MS" Howell</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8390</link>
		<dc:creator>Michael "I don't hate MS" Howell</dc:creator>
		<pubDate>Wed, 05 Aug 2009 00:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8390</guid>
		<description>I don&#039;t hate the new UI because it came from MS. I hate the new UI because I hate the new UI. Really.

I&#039;ll probably move to KOffice thanks to them.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t hate the new UI because it came from MS. I hate the new UI because I hate the new UI. Really.</p>
<p>I&#8217;ll probably move to KOffice thanks to them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jscurtu</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8387</link>
		<dc:creator>jscurtu</dc:creator>
		<pubDate>Tue, 04 Aug 2009 16:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8387</guid>
		<description>OMG... looks like OpenOffice is just not able to be innovative... I remember the announcement from OOo about a new UI that was planned, back then I was excited about it, but looking at this now... I not that sure about it... We will see when its done..</description>
		<content:encoded><![CDATA[<p>OMG&#8230; looks like OpenOffice is just not able to be innovative&#8230; I remember the announcement from OOo about a new UI that was planned, back then I was excited about it, but looking at this now&#8230; I not that sure about it&#8230; We will see when its done..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Čukić</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8386</link>
		<dc:creator>Ivan Čukić</dc:creator>
		<pubDate>Tue, 04 Aug 2009 16:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8386</guid>
		<description>@&lt;a href=&quot;#comment-8380&quot; rel=&quot;nofollow&quot;&gt;Erlend&lt;/a&gt;: Looks really don&#039;t enter into it. It takes too much of the workspace. And the /discoverability/ in this case is going to inspire the users to produce inconsistent documents by using the styles even less than they used to do before.

When editing a document, the focus should always be on the document and its contents, later on its looks, and never on the program in which you work.

The ribbon is perfect for the &#039;lets play with this thing to see what it can do&#039; use-case.

@&lt;a href=&quot;#comment-8382&quot; rel=&quot;nofollow&quot;&gt;Inge Wallin&lt;/a&gt;: And KOffice (AFAIK) doesn&#039;t have half the code in German :)

@&lt;a href=&quot;#comment-8384&quot; rel=&quot;nofollow&quot;&gt;jstaniek&lt;/a&gt;: Without any intention to dismiss anyone&#039;s work, Kexi isn&#039;t on my radar at all, and I don&#039;t really care about its UI. 

With that said, the current Kexi&#039;s UI (I&#039;ve just started the trunk version) is not completely like the one proposed for OOo. It still takes the same space as the menus + toolbar did, and not more.

p.s. It was fun to remember what the Oxygen looked like in 2007 :)</description>
		<content:encoded><![CDATA[<p>@<a class="atr_link" href="#comment-8380" rel="nofollow">Erlend</a>: Looks really don&#8217;t enter into it. It takes too much of the workspace. And the /discoverability/ in this case is going to inspire the users to produce inconsistent documents by using the styles even less than they used to do before.</p>
<p>When editing a document, the focus should always be on the document and its contents, later on its looks, and never on the program in which you work.</p>
<p>The ribbon is perfect for the &#8216;lets play with this thing to see what it can do&#8217; use-case.</p>
<p>@<a class="atr_link" href="#comment-8382" rel="nofollow">Inge Wallin</a>: And KOffice (AFAIK) doesn&#8217;t have half the code in German <img src='http://ivan.fomentgroup.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@<a class="atr_link" href="#comment-8384" rel="nofollow">jstaniek</a>: Without any intention to dismiss anyone&#8217;s work, Kexi isn&#8217;t on my radar at all, and I don&#8217;t really care about its UI. </p>
<p>With that said, the current Kexi&#8217;s UI (I&#8217;ve just started the trunk version) is not completely like the one proposed for OOo. It still takes the same space as the menus + toolbar did, and not more.</p>
<p>p.s. It was fun to remember what the Oxygen looked like in 2007 <img src='http://ivan.fomentgroup.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jstaniek</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8384</link>
		<dc:creator>jstaniek</dc:creator>
		<pubDate>Tue, 04 Aug 2009 15:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8384</guid>
		<description>Hi, I&#039;d like to mention that at least one KOffice app implements parts of the this kind of the GUI, e.g. see http://74.125.153.132/search?q=cache:Uv29sVU8l40J:www.kdedevelopers.org/node/2955 (mirrored)</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;d like to mention that at least one KOffice app implements parts of the this kind of the GUI, e.g. see <a href="http://74.125.153.132/search?q=cache:Uv29sVU8l40J:www.kdedevelopers.org/node/2955" rel="nofollow">http://74.125.153.132/search?q=cache:Uv29sVU8l40J:www.kdedevelopers.org/node/2955</a> (mirrored)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Inge Wallin</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8382</link>
		<dc:creator>Inge Wallin</dc:creator>
		<pubDate>Tue, 04 Aug 2009 15:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8382</guid>
		<description>The interesting thing is that if we *wanted* to do a GUI like that, we could do it with less than 1/10th of the resources that OOo has to put into it.  Their toolkit doesn&#039;t even have a layout manager, so everything has to be placed by hand.</description>
		<content:encoded><![CDATA[<p>The interesting thing is that if we *wanted* to do a GUI like that, we could do it with less than 1/10th of the resources that OOo has to put into it.  Their toolkit doesn&#8217;t even have a layout manager, so everything has to be placed by hand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erlend</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8380</link>
		<dc:creator>Erlend</dc:creator>
		<pubDate>Tue, 04 Aug 2009 15:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8380</guid>
		<description>i actually think this looks much better than the menu-driven office suits we have now. it certainly helps discoverability and makes it easier for us who don&#039;t use an office suite every day. for power-users, i guess the menus will still be present.

i really wish they would move the controls to the left or the right of the work area, though. most document editing is done in portrait mode.</description>
		<content:encoded><![CDATA[<p>i actually think this looks much better than the menu-driven office suits we have now. it certainly helps discoverability and makes it easier for us who don&#8217;t use an office suite every day. for power-users, i guess the menus will still be present.</p>
<p>i really wish they would move the controls to the left or the right of the work area, though. most document editing is done in portrait mode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Čukić</title>
		<link>http://ivan.fomentgroup.org/blog/2009/08/04/koffice-needs-you-and-we-need-koffice/comment-page-1/#comment-8379</link>
		<dc:creator>Ivan Čukić</dc:creator>
		<pubDate>Tue, 04 Aug 2009 14:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://ivan.fomentgroup.org/blog/?p=584#comment-8379</guid>
		<description>@&lt;a href=&quot;#comment-8377&quot; rel=&quot;nofollow&quot;&gt;Dion Moult&lt;/a&gt;: Yes, exactly. The proposed /new/ UI is really scaring me (like the majority of the commenters on the linked page)</description>
		<content:encoded><![CDATA[<p>@<a class="atr_link" href="#comment-8377" rel="nofollow">Dion Moult</a>: Yes, exactly. The proposed /new/ UI is really scaring me (like the majority of the commenters on the linked page)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
