<?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: Website Changes and the Value of Feedback</title>
	<atom:link href="http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 03:57:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Basil Vandegriend</title>
		<link>http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback/comment-page-1#comment-341</link>
		<dc:creator>Basil Vandegriend</dc:creator>
		<pubDate>Fri, 26 May 2006 03:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback#comment-341</guid>
		<description>I&#039;ve also heard of studies where reading comprehension suffers as the lines of text get longer beyond a certain point (but I don&#039;t have a reference either). 

For the comment box - its width is fixed. I&#039;d like to make its width proportional to the width of the article (which is dynamic based on your browser window size), but I don&#039;t know how to do that excluding complicated javascript tricks. So I tried making the comment box as large as possible without impacting smaller screen resolutions.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also heard of studies where reading comprehension suffers as the lines of text get longer beyond a certain point (but I don&#8217;t have a reference either). </p>
<p>For the comment box &#8211; its width is fixed. I&#8217;d like to make its width proportional to the width of the article (which is dynamic based on your browser window size), but I don&#8217;t know how to do that excluding complicated javascript tricks. So I tried making the comment box as large as possible without impacting smaller screen resolutions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Gamble</title>
		<link>http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback/comment-page-1#comment-340</link>
		<dc:creator>Justin Gamble</dc:creator>
		<pubDate>Fri, 26 May 2006 00:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2006/website-changes-and-the-value-of-feedback#comment-340</guid>
		<description>I also prefer extra white space.  Personally I don&#039;t consider it a &quot;waste&quot;, because it helps to organize the content better and makes it easier to understand.

I recall a psychology study that was done (maybe someone can find a link to it?) whereby a one-page piece of writing was presented to 2 groups.  The page was identical, except that one group had a subject line, and the other group didn&#039;t (it just started rambling, but without a subject line).  The comprehension level of the group with the subject line was substantially higher.  Why?  Presumably because the way the human mind works, the subject line allowed people to properly categorize the information they were receiving.

Subject lines are obviously different from blank spaces, but perhaps the same argument could be said about useful blank spaces inserted in key locations?

A side-perk of the white space on the sides.. is that it encourages a more condensed article in-between the sidelines, which presumably is a good thing.  :-)

My only suggestion at this time.. is maybe to make the comment box wider?  I notice the article text is wider than the comment box.  Are you saying that the article text is more important than the feedback that I am now offering!??  :-)</description>
		<content:encoded><![CDATA[<p>I also prefer extra white space.  Personally I don&#8217;t consider it a &#8220;waste&#8221;, because it helps to organize the content better and makes it easier to understand.</p>
<p>I recall a psychology study that was done (maybe someone can find a link to it?) whereby a one-page piece of writing was presented to 2 groups.  The page was identical, except that one group had a subject line, and the other group didn&#8217;t (it just started rambling, but without a subject line).  The comprehension level of the group with the subject line was substantially higher.  Why?  Presumably because the way the human mind works, the subject line allowed people to properly categorize the information they were receiving.</p>
<p>Subject lines are obviously different from blank spaces, but perhaps the same argument could be said about useful blank spaces inserted in key locations?</p>
<p>A side-perk of the white space on the sides.. is that it encourages a more condensed article in-between the sidelines, which presumably is a good thing.  :-)</p>
<p>My only suggestion at this time.. is maybe to make the comment box wider?  I notice the article text is wider than the comment box.  Are you saying that the article text is more important than the feedback that I am now offering!??  :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

