<?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 on: User relevant information</title>
	<atom:link href="http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/</link>
	<description>the drawing table</description>
	<lastBuildDate>Sat, 21 Feb 2009 07:56:49 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bruno Silva</title>
		<link>http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-230</link>
		<dc:creator>Bruno Silva</dc:creator>
		<pubDate>Tue, 18 Sep 2007 14:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-230</guid>
		<description>You&#039;re right about the identity part. An application must use wisely its resources and avoid too much configuration. Most of the time all that configuration is unnecessary, most people will stay with the default configuration if it rocks, so that extra coding work and extra cycles on the client machine will be completely useless.

About the strong colors in windows alphas you&#039;re right, and I&#039;ve mentioned that if you choose to present the information on top, the bar must have very light colors.

As for the Digital Catalog content I have to disagree, I don&#039;t know if you missunderstood me or something, but I didn&#039;t want to represent DC with any of those screens, just the specific scenario on the listview, of course the treeview will remain with current data. So, showing the details of an item in the listview, inside the listitem, would work very well, and since WPF can adapt its visual to the type of content you could easily create different templates for each type of object (category, volume, folder, file...).</description>
		<content:encoded><![CDATA[<p>You&#8217;re right about the identity part. An application must use wisely its resources and avoid too much configuration. Most of the time all that configuration is unnecessary, most people will stay with the default configuration if it rocks, so that extra coding work and extra cycles on the client machine will be completely useless.</p>
<p>About the strong colors in windows alphas you&#8217;re right, and I&#8217;ve mentioned that if you choose to present the information on top, the bar must have very light colors.</p>
<p>As for the Digital Catalog content I have to disagree, I don&#8217;t know if you missunderstood me or something, but I didn&#8217;t want to represent DC with any of those screens, just the specific scenario on the listview, of course the treeview will remain with current data. So, showing the details of an item in the listview, inside the listitem, would work very well, and since WPF can adapt its visual to the type of content you could easily create different templates for each type of object (category, volume, folder, file&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thylux</title>
		<link>http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-229</link>
		<dc:creator>thylux</dc:creator>
		<pubDate>Tue, 18 Sep 2007 14:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-229</guid>
		<description>Customization by the user is something to be careful messing with. Over-customization will lead to the loss of the identity of the applications&#039; interface and is always a good source of bugs and performance losses that may drive users away.
I&#039;m not against customization... As a user to many applications i believe that to be able to choose some aspects of my experience is very important. But, sometimes it&#039;s better to not customize than doing it wrong. In the case of that particular aspect of Digital Catalog, i think it should be sufficient to use different background color when those fields have values, so that the user can easily perceive that there&#039;s something written, as you&#039;ve already stated.
What Windows Vista had in their alpha releases to bring attention up to the bar was not only its position, but also its strong colors. But it&#039;s too aggressive...

I like the solution you&#039;ve presented with the &#039;Contacts&#039; window, because that would permit a more natural way to show/hide the information and would also allow to template the information bar to better match the type of contents to show.

In the case of having the information with the item, it wouldn&#039;t work so great in Digital Catalog, because of its hierarchical structure. Too confusing... Because of the number of indents to the information and the amount information necessary to present in itself.

That version of Digital Catalog is built in Windows Forms, that isn&#039;t that easily flexible to implement such solutions, but i hope that with WPF in the UX version that won&#039;t be a problem...</description>
		<content:encoded><![CDATA[<p>Customization by the user is something to be careful messing with. Over-customization will lead to the loss of the identity of the applications&#8217; interface and is always a good source of bugs and performance losses that may drive users away.<br />
I&#8217;m not against customization&#8230; As a user to many applications i believe that to be able to choose some aspects of my experience is very important. But, sometimes it&#8217;s better to not customize than doing it wrong. In the case of that particular aspect of Digital Catalog, i think it should be sufficient to use different background color when those fields have values, so that the user can easily perceive that there&#8217;s something written, as you&#8217;ve already stated.<br />
What Windows Vista had in their alpha releases to bring attention up to the bar was not only its position, but also its strong colors. But it&#8217;s too aggressive&#8230;</p>
<p>I like the solution you&#8217;ve presented with the &#8216;Contacts&#8217; window, because that would permit a more natural way to show/hide the information and would also allow to template the information bar to better match the type of contents to show.</p>
<p>In the case of having the information with the item, it wouldn&#8217;t work so great in Digital Catalog, because of its hierarchical structure. Too confusing&#8230; Because of the number of indents to the information and the amount information necessary to present in itself.</p>
<p>That version of Digital Catalog is built in Windows Forms, that isn&#8217;t that easily flexible to implement such solutions, but i hope that with WPF in the UX version that won&#8217;t be a problem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno Silva</title>
		<link>http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-225</link>
		<dc:creator>Bruno Silva</dc:creator>
		<pubDate>Mon, 17 Sep 2007 18:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-225</guid>
		<description>Right, I agree, but I think we should provide an excelent out-of-the-box experience. Such experience shouldn&#039;t require the user to customize his interface, everything should be &quot;right there&quot; (or not, depending on the case). And my question is about the best experience for most users.</description>
		<content:encoded><![CDATA[<p>Right, I agree, but I think we should provide an excelent out-of-the-box experience. Such experience shouldn&#8217;t require the user to customize his interface, everything should be &#8220;right there&#8221; (or not, depending on the case). And my question is about the best experience for most users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zEro</title>
		<link>http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-222</link>
		<dc:creator>zEro</dc:creator>
		<pubDate>Mon, 17 Sep 2007 15:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpfbox.wordpress.com/2007/09/13/user-relevant-information/#comment-222</guid>
		<description>Nice article!
What i think about the subject, is that the user should make his choice! We, programmers, designers, etc, should provide the user with several options, and he should choose in accordance with  its necessities. What is relevant information for one user, maybe it isn&#039;t for another, i think nowadays, customization is the right attitude, implementing that, it&#039;s another story!</description>
		<content:encoded><![CDATA[<p>Nice article!<br />
What i think about the subject, is that the user should make his choice! We, programmers, designers, etc, should provide the user with several options, and he should choose in accordance with  its necessities. What is relevant information for one user, maybe it isn&#8217;t for another, i think nowadays, customization is the right attitude, implementing that, it&#8217;s another story!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
