<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: GNOME Summit control-center summary</title>
	<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/</link>
	<description>From lost to the river</description>
	<pubDate>Sun, 06 Jul 2008 01:28:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: GNOME Summit, day 3 &#171; fishsoup</title>
		<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-535</link>
		<dc:creator>GNOME Summit, day 3 &#171; fishsoup</dc:creator>
		<pubDate>Tue, 09 Oct 2007 16:42:46 +0000</pubDate>
		<guid>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-535</guid>
		<description>[...] Summit, day&#160;3  Day 3 started 10:00 with summaries. Rodrigo gave a detailed summary of the control center discussion the previous day, and we had quick reports from the other sessions [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Summit, day&nbsp;3  Day 3 started 10:00 with summaries. Rodrigo gave a detailed summary of the control center discussion the previous day, and we had quick reports from the other sessions [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Van den Bosch</title>
		<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-534</link>
		<dc:creator>Peter Van den Bosch</dc:creator>
		<pubDate>Mon, 08 Oct 2007 21:45:55 +0000</pubDate>
		<guid>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-534</guid>
		<description>like the ideas for integrating the capplets very much!
Some other feedback:
* keyboard shortcuts does seem something 'else' than other keyboard configuration. I would leave it out because it also has something to do with controlling the desktop and applications, not just the keyboard.
* screen applet with resolution and xrandr is okay, but selecting screensaver seems again less coherent with the rest.
* pulseaudio: I'm all for pulseaudio replacing esound, but the current configuration windows of pulse are too techy (sources, sinks, etc). I hope users won't have to use them by default.
* I'd leave typing break as part of the configuration window, it should always be configurable, not only on first time or usage, and is different from screensaver settings.
* about keyboard a11y: 
** the current 'enable keyboard accessibility functions' checkbox is a bit weird from user perspective (why necessary, why does it disable only part of the configs)
** there should be a link from the mouse capplet to mouse keys, because that's where people go first when having problems using the mouse

Links between related capplets are good since they make finding things easier. But I think real links (like in blue and underlined) should be used in stead of buttons. People know them very well from the internet anyway so they know they can click on it without doing anything wrong. Buttons on the other hand give the impression that something will be changed and make the user interface feel more complicated (they jump out of the background). In the eclipse IDE for example, they are very handy without cluttering the UI even more.</description>
		<content:encoded><![CDATA[<p>like the ideas for integrating the capplets very much!<br />
Some other feedback:<br />
* keyboard shortcuts does seem something &#8216;else&#8217; than other keyboard configuration. I would leave it out because it also has something to do with controlling the desktop and applications, not just the keyboard.<br />
* screen applet with resolution and xrandr is okay, but selecting screensaver seems again less coherent with the rest.<br />
* pulseaudio: I&#8217;m all for pulseaudio replacing esound, but the current configuration windows of pulse are too techy (sources, sinks, etc). I hope users won&#8217;t have to use them by default.<br />
* I&#8217;d leave typing break as part of the configuration window, it should always be configurable, not only on first time or usage, and is different from screensaver settings.<br />
* about keyboard a11y:<br />
** the current &#8216;enable keyboard accessibility functions&#8217; checkbox is a bit weird from user perspective (why necessary, why does it disable only part of the configs)<br />
** there should be a link from the mouse capplet to mouse keys, because that&#8217;s where people go first when having problems using the mouse</p>
<p>Links between related capplets are good since they make finding things easier. But I think real links (like in blue and underlined) should be used in stead of buttons. People know them very well from the internet anyway so they know they can click on it without doing anything wrong. Buttons on the other hand give the impression that something will be changed and make the user interface feel more complicated (they jump out of the background). In the eclipse IDE for example, they are very handy without cluttering the UI even more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Burton</title>
		<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-533</link>
		<dc:creator>Ross Burton</dc:creator>
		<pubDate>Mon, 08 Oct 2007 19:09:57 +0000</pubDate>
		<guid>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-533</guid>
		<description>I'm not dissing anyone in particular, but I wanted a slab-like interface for the new &lt;a href="http://pokylinux.org/images/sato/desktop.png" rel="nofollow"&gt;Matchbox Desktop&lt;/a&gt; and after reviewing libslab decided it was dramaticaly over-complicated.

&lt;a href="http://svn.o-hand.com/repos/matchbox/trunk/matchbox-desktop-2/libtaku" rel="nofollow"&gt;libtaku&lt;/a&gt;, the slab clone in Matchbox Desktop (and Dates, and OpenMoko's Today application) is 1600 lines of code in total.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not dissing anyone in particular, but I wanted a slab-like interface for the new <a href="http://pokylinux.org/images/sato/desktop.png" rel="nofollow">Matchbox Desktop</a> and after reviewing libslab decided it was dramaticaly over-complicated.</p>
<p><a href="http://svn.o-hand.com/repos/matchbox/trunk/matchbox-desktop-2/libtaku" rel="nofollow">libtaku</a>, the slab clone in Matchbox Desktop (and Dates, and OpenMoko&#8217;s Today application) is 1600 lines of code in total.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peteris Krisjanis</title>
		<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-532</link>
		<dc:creator>Peteris Krisjanis</dc:creator>
		<pubDate>Mon, 08 Oct 2007 19:01:56 +0000</pubDate>
		<guid>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-532</guid>
		<description>Two questions - why list is talking about something new, why not restore gnome-control-center efforts? And what PulseAudio is doing there? Yes, When I install it, I will get nice control applet, but before that...</description>
		<content:encoded><![CDATA[<p>Two questions - why list is talking about something new, why not restore gnome-control-center efforts? And what PulseAudio is doing there? Yes, When I install it, I will get nice control applet, but before that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: no one in particular</title>
		<link>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-531</link>
		<dc:creator>no one in particular</dc:creator>
		<pubDate>Mon, 08 Oct 2007 17:10:27 +0000</pubDate>
		<guid>http://blogs.gnome.org/rodrigo/2007/10/08/gnome-summit-control-center-summary/#comment-531</guid>
		<description>Just one comment: I really don't think typing break should be moved to screensaver settings.  Sure, they're both things that are triggered by time delays... or something?  But I don't see how they're really related at all.  One is for locking and blanking the screen, the other to rest your hands.  They really just don't seem related at all to me.</description>
		<content:encoded><![CDATA[<p>Just one comment: I really don&#8217;t think typing break should be moved to screensaver settings.  Sure, they&#8217;re both things that are triggered by time delays&#8230; or something?  But I don&#8217;t see how they&#8217;re really related at all.  One is for locking and blanking the screen, the other to rest your hands.  They really just don&#8217;t seem related at all to me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
