<?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"
	>
<channel>
	<title>Comments on: Conduit UI Experiments</title>
	<atom:link href="http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/</link>
	<description>Who needs facts when you have anecdotal evidence?</description>
	<pubDate>Sat, 04 Feb 2012 12:21:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Theme colors &#171; Project Hamster</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-30284</link>
		<dc:creator>Theme colors &#171; Project Hamster</dc:creator>
		<pubDate>Tue, 23 Feb 2010 11:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-30284</guid>
		<description>[...] Clearlooks. It is not the same as the one found in your preferences, because elements need states. (John Stowers has a much nicer script to regenerate colors for your current [...]</description>
		<content:encoded><![CDATA[<p>[...] Clearlooks. It is not the same as the one found in your preferences, because elements need states. (John Stowers has a much nicer script to regenerate colors for your current [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy fitzsimon</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26971</link>
		<dc:creator>andy fitzsimon</dc:creator>
		<pubDate>Mon, 04 Aug 2008 09:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26971</guid>
		<description>very cool colour preview app mate.   
Thos should totally include that as the default interface for editing colour classes in gtk themes</description>
		<content:encoded><![CDATA[<p>very cool colour preview app mate.<br />
Thos should totally include that as the default interface for editing colour classes in gtk themes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Conduit UI Experiments - Some Conclusions Johns Blog</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26957</link>
		<dc:creator>&#187; Conduit UI Experiments - Some Conclusions Johns Blog</dc:creator>
		<pubDate>Sun, 03 Aug 2008 13:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26957</guid>
		<description>[...] once again to the many people who commented on my last two blog posts. All the feedback has been gratefully received. I just released Conduit 0.3.13 which, amongst [...]</description>
		<content:encoded><![CDATA[<p>[...] once again to the many people who commented on my last two blog posts. All the feedback has been gratefully received. I just released Conduit 0.3.13 which, amongst [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Conduit UI Experiments - Part Two Johns Blog</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26903</link>
		<dc:creator>&#187; Conduit UI Experiments - Part Two Johns Blog</dc:creator>
		<pubDate>Thu, 31 Jul 2008 23:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26903</guid>
		<description>[...] you everyone for their constructive comments on my previous post. A number of posters suggested the rounded boxes that conduit uses to group [...]</description>
		<content:encoded><![CDATA[<p>[...] you everyone for their constructive comments on my previous post. A number of posters suggested the rounded boxes that conduit uses to group [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dr88dr88</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26901</link>
		<dc:creator>dr88dr88</dc:creator>
		<pubDate>Thu, 31 Jul 2008 16:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26901</guid>
		<description>You should move the message to the top instead of the bottom. Gedit en firefox place it in the top so users are used to that.</description>
		<content:encoded><![CDATA[<p>You should move the message to the top instead of the bottom. Gedit en firefox place it in the top so users are used to that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fergus</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26900</link>
		<dc:creator>fergus</dc:creator>
		<pubDate>Thu, 31 Jul 2008 16:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26900</guid>
		<description>The GUI could use some help but a decent Users Guide would be better.  Something that explains what each source/sink does and how to properly configure it.  What to expect when syncing to/from different sources/sinks.  Not all source/sink combinations make sense.  If I am creating a new sync group how do I know which sink works with what source?  Some simple documentation would go along way!</description>
		<content:encoded><![CDATA[<p>The GUI could use some help but a decent Users Guide would be better.  Something that explains what each source/sink does and how to properly configure it.  What to expect when syncing to/from different sources/sinks.  Not all source/sink combinations make sense.  If I am creating a new sync group how do I know which sink works with what source?  Some simple documentation would go along way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob J. Caskey</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26899</link>
		<dc:creator>Rob J. Caskey</dc:creator>
		<pubDate>Thu, 31 Jul 2008 14:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26899</guid>
		<description>USB printers plug in and just work. There is also a separate application for viewing and managing some more obscure options that we computer dorks love and always use. Most users do everything they need to from the print dialog. So should it be for device sync. That's what users expect from something that is part of Gnome, that you can plug it in and use it from your application right away.</description>
		<content:encoded><![CDATA[<p>USB printers plug in and just work. There is also a separate application for viewing and managing some more obscure options that we computer dorks love and always use. Most users do everything they need to from the print dialog. So should it be for device sync. That&#8217;s what users expect from something that is part of Gnome, that you can plug it in and use it from your application right away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26898</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Thu, 31 Jul 2008 13:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26898</guid>
		<description>What Brad Griffith said!</description>
		<content:encoded><![CDATA[<p>What Brad Griffith said!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26896</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 31 Jul 2008 13:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26896</guid>
		<description>PS: wouldnt Conduit also fill a much needed niche of a good integrated backup tool for Gnome?</description>
		<content:encoded><![CDATA[<p>PS: wouldnt Conduit also fill a much needed niche of a good integrated backup tool for Gnome?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26895</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 31 Jul 2008 13:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnstowers.co.nz/blog/index.php/2008/07/31/conduit-ui-experiments/#comment-26895</guid>
		<description>User perspective: Conduit UI is currently an "advanced" configuration tool

Correct me if I'm wrong, but isn't Conduit also meant for one-time syncs as well? I don't understand how that would work in the current UI

My idea of how conduit would work assuming mentioned applications use Conduit to sync:
- Attach Phone to computer
- open Banshee, where phone shows as external source
- drag playlist from library to phone, Conduit dialog asks if I want to always sync to playlist
- open Contacts (Pimlico) - choose sync contacts from menu
- dialog opens with single element of above UI showing contacts as source (with option to make target) and potential targets on left. A tick box for always sync would be present. A "Advanced Setup" option could be present as well. Sync!

another option to all the application integration is a nautilus left click option to sync phone/iPod, which would bring up a UI with only supported sources available, checking off which ones you want synced.

Another example for transferring a movie to Youtube: there should be a left click option in nautilus to "post online" or "upload to.." - file would be recognized as a video and a dialog would offer the supported video sites.

basically the current UI is overkill for the majority of user operations, especially when considering one-time sync. Although the full power should be underneath, users like me don't want to see all the choices every time. We want to see the options that make the most sense for that operation and then be able to dive deeper if what we want isnt there.

think "dynamic focused workflow" rather than "hears everything you can possibly do"</description>
		<content:encoded><![CDATA[<p>User perspective: Conduit UI is currently an &#8220;advanced&#8221; configuration tool</p>
<p>Correct me if I&#8217;m wrong, but isn&#8217;t Conduit also meant for one-time syncs as well? I don&#8217;t understand how that would work in the current UI</p>
<p>My idea of how conduit would work assuming mentioned applications use Conduit to sync:<br />
- Attach Phone to computer<br />
- open Banshee, where phone shows as external source<br />
- drag playlist from library to phone, Conduit dialog asks if I want to always sync to playlist<br />
- open Contacts (Pimlico) - choose sync contacts from menu<br />
- dialog opens with single element of above UI showing contacts as source (with option to make target) and potential targets on left. A tick box for always sync would be present. A &#8220;Advanced Setup&#8221; option could be present as well. Sync!</p>
<p>another option to all the application integration is a nautilus left click option to sync phone/iPod, which would bring up a UI with only supported sources available, checking off which ones you want synced.</p>
<p>Another example for transferring a movie to Youtube: there should be a left click option in nautilus to &#8220;post online&#8221; or &#8220;upload to..&#8221; - file would be recognized as a video and a dialog would offer the supported video sites.</p>
<p>basically the current UI is overkill for the majority of user operations, especially when considering one-time sync. Although the full power should be underneath, users like me don&#8217;t want to see all the choices every time. We want to see the options that make the most sense for that operation and then be able to dive deeper if what we want isnt there.</p>
<p>think &#8220;dynamic focused workflow&#8221; rather than &#8220;hears everything you can possibly do&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

