<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Thorsten's Weblog</title>
	<atom:link href="http://blog.thebehrens.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thebehrens.net</link>
	<description>In the trenches with OpenOffice.org's graphic subsystems</description>
	<lastBuildDate>Sun, 22 Nov 2009 23:00:34 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on GSoC Mentor Summit 2009 by Upgrading homeserver hardware &#171; Thorsten&#8217;s Weblog</title>
		<link>http://blog.thebehrens.net/2009/11/09/gsoc-mentor-summit-2009/#comment-753</link>
		<dc:creator>Upgrading homeserver hardware &#171; Thorsten&#8217;s Weblog</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=294#comment-753</guid>
		<description>[...] while staying at the GSoC mentor summit, things suddenly went south, the SparcStation blew its scsi controller (and the attached [...]</description>
		<content:encoded><![CDATA[<p>[...] while staying at the GSoC mentor summit, things suddenly went south, the SparcStation blew its scsi controller (and the attached [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GSoC 2009 Wrap-Up by thorstenb</title>
		<link>http://blog.thebehrens.net/2009/10/24/gsoc-2009-wrap-up/#comment-749</link>
		<dc:creator>thorstenb</dc:creator>
		<pubDate>Mon, 16 Nov 2009 07:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=284#comment-749</guid>
		<description>Hey Nelle, yep, am aware of that; just happy that Jon is back at working at OOo. Let&#039;s sort out the tablet problem on irc.</description>
		<content:encoded><![CDATA[<p>Hey Nelle, yep, am aware of that; just happy that Jon is back at working at OOo. Let&#8217;s sort out the tablet problem on irc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GSoC 2009 Wrap-Up by Nelle</title>
		<link>http://blog.thebehrens.net/2009/10/24/gsoc-2009-wrap-up/#comment-748</link>
		<dc:creator>Nelle</dc:creator>
		<pubDate>Sun, 15 Nov 2009 15:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=284#comment-748</guid>
		<description>Hi, 
I&#039;m the team manager on the project we&#039;re doing at Centrale Nantes, with Jon

We&#039;re not working on OCR integration, but on the improving ink annotations on Impress, when working with a tablet PC.

We have a blog at: https://pedagogie.ec-nantes.fr/tablet-pc/

Unfortunately, there seems to be a problem right now. If you have any questions, I&#039;m often on the IRC chanel educooo.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I&#8217;m the team manager on the project we&#8217;re doing at Centrale Nantes, with Jon</p>
<p>We&#8217;re not working on OCR integration, but on the improving ink annotations on Impress, when working with a tablet PC.</p>
<p>We have a blog at: <a href="https://pedagogie.ec-nantes.fr/tablet-pc/" rel="nofollow">https://pedagogie.ec-nantes.fr/tablet-pc/</a></p>
<p>Unfortunately, there seems to be a problem right now. If you have any questions, I&#8217;m often on the IRC chanel educooo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ODF Plugfest &amp; OOoCon 2009 by Alvin</title>
		<link>http://blog.thebehrens.net/2009/11/09/odf-plugfest-ooocon-2009/#comment-743</link>
		<dc:creator>Alvin</dc:creator>
		<pubDate>Mon, 09 Nov 2009 22:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=300#comment-743</guid>
		<description>The slides of Kohei show how much valuable changes happen in Calc. They did a great job and didn&#039;t mention everything that was done (copying multiple selections for example) so far. Just great work.

Thanks OOo-devs for this great product.</description>
		<content:encoded><![CDATA[<p>The slides of Kohei show how much valuable changes happen in Calc. They did a great job and didn&#8217;t mention everything that was done (copying multiple selections for example) so far. Just great work.</p>
<p>Thanks OOo-devs for this great product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GSoC 2009 Wrap-Up by Aldi</title>
		<link>http://blog.thebehrens.net/2009/10/24/gsoc-2009-wrap-up/#comment-720</link>
		<dc:creator>Aldi</dc:creator>
		<pubDate>Sun, 25 Oct 2009 06:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=284#comment-720</guid>
		<description>Welcome back Jon!
This sounds very good. I hope that your new project has something to do with OCR integration :-)</description>
		<content:encoded><![CDATA[<p>Welcome back Jon!<br />
This sounds very good. I hope that your new project has something to do with OCR integration <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Let There Be Summer! by GSoC 2009 Wrap-Up &#171; Thorsten&#8217;s Weblog</title>
		<link>http://blog.thebehrens.net/2009/04/20/let-there-be-summer/#comment-718</link>
		<dc:creator>GSoC 2009 Wrap-Up &#171; Thorsten&#8217;s Weblog</dc:creator>
		<pubDate>Sat, 24 Oct 2009 13:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/?p=199#comment-718</guid>
		<description>[...] gsoc    With the mentor summit coming up, it&#8217;s high time to wrap up this year&#8217;s Google Summer of Code for ooo-build. We started the term with 6 students, of which one was sadly missing in action right from the [...]</description>
		<content:encoded><![CDATA[<p>[...] gsoc    With the mentor summit coming up, it&#8217;s high time to wrap up this year&#8217;s Google Summer of Code for ooo-build. We started the term with 6 students, of which one was sadly missing in action right from the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A comment on the Renaissance prototype survey results by thorstenb</title>
		<link>http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-707</link>
		<dc:creator>thorstenb</dc:creator>
		<pubDate>Fri, 09 Oct 2009 18:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-707</guid>
		<description>&quot;doesn&#039;t necessarily mean&quot; - well, that&#039;s also interpreting a lot into the data, isn&#039;t it? ;)

So frankly, seeing that nearly half of the respondents where not positive of the change (and of course the outcries of individuals over the recent weeks, regarding renaissance), made me think that it would be a huge boon to &lt;em&gt;not&lt;/em&gt; do the same mistake MS did, in not offering a choice. Nothing more, nothing less.

Regarding the rest of your answer - if we don&#039;t have resources to do a new UI properly, why are we then doing it in the first place? Making the old one incrementally better would be by far the better approach, from a business perspective (if this assumption would be true). My problem is: UI quite quickly looks outdated. If we now throw everything onto hardcoding a new one, the next fad two years in the future will &lt;em&gt;again&lt;/em&gt; make us look old. So &lt;em&gt;if&lt;/em&gt; we go &amp; change something, then at least in a way that makes it easy for non-programmers to substantially change UI. Everything else is just a waste of time, in my book.</description>
		<content:encoded><![CDATA[<p>&#8220;doesn&#8217;t necessarily mean&#8221; &#8211; well, that&#8217;s also interpreting a lot into the data, isn&#8217;t it? <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>So frankly, seeing that nearly half of the respondents where not positive of the change (and of course the outcries of individuals over the recent weeks, regarding renaissance), made me think that it would be a huge boon to <em>not</em> do the same mistake MS did, in not offering a choice. Nothing more, nothing less.</p>
<p>Regarding the rest of your answer &#8211; if we don&#8217;t have resources to do a new UI properly, why are we then doing it in the first place? Making the old one incrementally better would be by far the better approach, from a business perspective (if this assumption would be true). My problem is: UI quite quickly looks outdated. If we now throw everything onto hardcoding a new one, the next fad two years in the future will <em>again</em> make us look old. So <em>if</em> we go &amp; change something, then at least in a way that makes it easy for non-programmers to substantially change UI. Everything else is just a waste of time, in my book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A comment on the Renaissance prototype survey results by Frank Schönheit</title>
		<link>http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-704</link>
		<dc:creator>Frank Schönheit</dc:creator>
		<pubDate>Fri, 09 Oct 2009 10:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-704</guid>
		<description>Tommy,

since you posted this in reply to my comment, I cannot refrain from replying, too:

Requesting to stop the entire project, because of the misinterpretation (of something you saw in the prototypes) as ribbons, and completely ignoring and declining the potential of the project, and the work done by the involved people, is both ridiculous and insolent.

Spamming this (and probably other) place (3 out of the 10 comments so far are advertisements for your petition) with the request to sign the petition doesn&#039;t add to it&#039;s popularity, either.

Frank</description>
		<content:encoded><![CDATA[<p>Tommy,</p>
<p>since you posted this in reply to my comment, I cannot refrain from replying, too:</p>
<p>Requesting to stop the entire project, because of the misinterpretation (of something you saw in the prototypes) as ribbons, and completely ignoring and declining the potential of the project, and the work done by the involved people, is both ridiculous and insolent.</p>
<p>Spamming this (and probably other) place (3 out of the 10 comments so far are advertisements for your petition) with the request to sign the petition doesn&#8217;t add to it&#8217;s popularity, either.</p>
<p>Frank</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A comment on the Renaissance prototype survey results by Tommy</title>
		<link>http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-700</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Fri, 09 Oct 2009 10:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-700</guid>
		<description>please, sign the petition:
http://www.petitionspot.com/petitions/stoprenaissance/


627 signatures right now.
we must reach 1000</description>
		<content:encoded><![CDATA[<p>please, sign the petition:<br />
<a href="http://www.petitionspot.com/petitions/stoprenaissance/" rel="nofollow">http://www.petitionspot.com/petitions/stoprenaissance/</a></p>
<p>627 signatures right now.<br />
we must reach 1000</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A comment on the Renaissance prototype survey results by Frank Schoenheit</title>
		<link>http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-698</link>
		<dc:creator>Frank Schoenheit</dc:creator>
		<pubDate>Fri, 09 Oct 2009 08:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thebehrens.net/2009/09/30/a-comment-on-the-renaissance-prototype-survey-results/#comment-698</guid>
		<description>Thorsten,

No, we won&#039;t piss of a third of our user base. At least, I fail to read this from the charts: Just because people disagree to the need of a complete (!) overhaul, or disagree to the &quot;too many steps&quot; statement, doesn&#039;t necessarily imply they would be pissed of by a new UI. IMO, that&#039;s reading too much from the data.

About the UI framework thingie ... well, nice idea. Nothing new :), but nice. As nice as it has been during the last 10 years, and equally illusionary, in my opinion. We don&#039;t even have Dev and QA resources to provide *one* good, consistent, usable UI. How should we ever be able to provide multiple of them?

If there is a agreement or even only accepted statement that an overhaul of the UI should happen, then we should focus our scarce resources on making this one new UI excellent.

If we can do this by creating an framework (well, extending the existing, already pretty good, IMO) - fine. But let&#039;s do only one &quot;standard&quot; UI for it, and leave the rest to interested parties.</description>
		<content:encoded><![CDATA[<p>Thorsten,</p>
<p>No, we won&#8217;t piss of a third of our user base. At least, I fail to read this from the charts: Just because people disagree to the need of a complete (!) overhaul, or disagree to the &#8220;too many steps&#8221; statement, doesn&#8217;t necessarily imply they would be pissed of by a new UI. IMO, that&#8217;s reading too much from the data.</p>
<p>About the UI framework thingie &#8230; well, nice idea. Nothing new <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> , but nice. As nice as it has been during the last 10 years, and equally illusionary, in my opinion. We don&#8217;t even have Dev and QA resources to provide *one* good, consistent, usable UI. How should we ever be able to provide multiple of them?</p>
<p>If there is a agreement or even only accepted statement that an overhaul of the UI should happen, then we should focus our scarce resources on making this one new UI excellent.</p>
<p>If we can do this by creating an framework (well, extending the existing, already pretty good, IMO) &#8211; fine. But let&#8217;s do only one &#8220;standard&#8221; UI for it, and leave the rest to interested parties.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
