<?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: Mental Workload for Paged and Scrolled Documents</title>
	<atom:link href="http://www.standards-schmandards.com/2007/paged-or-scrolled/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/</link>
	<description>A pragmatic approach to web standards and accessibility</description>
	<pubDate>Sun, 06 Jul 2008 08:44:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: شات</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-47054</link>
		<dc:creator>شات</dc:creator>
		<pubDate>Fri, 13 Jun 2008 03:58:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-47054</guid>
		<description>Nice Info

Thanks</description>
		<content:encoded><![CDATA[<p>Nice Info</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vienna</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-22951</link>
		<dc:creator>Vienna</dc:creator>
		<pubDate>Tue, 16 Oct 2007 05:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-22951</guid>
		<description>putting the text into separate pages would mean more time needed to load the whole thing, and takes time to find/understand how to use the navigation buttons. with good internet speed and great webpage design it would be better, but that just doesn't come often enough to me.</description>
		<content:encoded><![CDATA[<p>putting the text into separate pages would mean more time needed to load the whole thing, and takes time to find/understand how to use the navigation buttons. with good internet speed and great webpage design it would be better, but that just doesn&#8217;t come often enough to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aggregatore News sui Motori di Ricerca &#187; Bookmark: design e interfacce</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-20354</link>
		<dc:creator>Aggregatore News sui Motori di Ricerca &#187; Bookmark: design e interfacce</dc:creator>
		<pubDate>Wed, 26 Sep 2007 13:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-20354</guid>
		<description>[...] da esempi reali per progettare una navigazione di paginazione efficace. Rimanendo in tema, Mental Workload for Paged and Scrolled Documents presenta uno studio sulla consultabilità di pagine con scrolling o contenuti paginati. Il [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] da esempi reali per progettare una navigazione di paginazione efficace. Rimanendo in tema, Mental Workload for Paged and Scrolled Documents presenta uno studio sulla consultabilità di pagine con scrolling o contenuti paginati. Il [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aggregatore News sui Motori di Ricerca &#187; Bookmark: design e interfacce</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-20355</link>
		<dc:creator>Aggregatore News sui Motori di Ricerca &#187; Bookmark: design e interfacce</dc:creator>
		<pubDate>Wed, 26 Sep 2007 13:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-20355</guid>
		<description>[...] da esempi reali per progettare una navigazione di paginazione efficace. Rimanendo in tema, Mental Workload for Paged and Scrolled Documents presenta uno studio sulla consultabilità di pagine con scrolling o contenuti paginati. Il [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] da esempi reali per progettare una navigazione di paginazione efficace. Rimanendo in tema, Mental Workload for Paged and Scrolled Documents presenta uno studio sulla consultabilità di pagine con scrolling o contenuti paginati. Il [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shraddha rusia starletexports</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-16433</link>
		<dc:creator>shraddha rusia starletexports</dc:creator>
		<pubDate>Thu, 16 Aug 2007 13:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-16433</guid>
		<description>it's a excellent readability test</description>
		<content:encoded><![CDATA[<p>it&#8217;s a excellent readability test</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Krantz</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13794</link>
		<dc:creator>Peter Krantz</dc:creator>
		<pubDate>Wed, 11 Jul 2007 11:36:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13794</guid>
		<description>Jonas: Splitting text into reasonably similar chunks may be simple. But how would you accomodate for different text size setting in the user's browser? Your calculated chunk may fit nicely with the default text size but may incur scrolling for larger sizes.

I guess the issue of focus may depend on what type of content you are providing. Is it a text that you want the reader to read carefully or just scan? On second thought it may not matter what you as a publisher want. It is all up to the reader I guess.</description>
		<content:encoded><![CDATA[<p>Jonas: Splitting text into reasonably similar chunks may be simple. But how would you accomodate for different text size setting in the user&#8217;s browser? Your calculated chunk may fit nicely with the default text size but may incur scrolling for larger sizes.</p>
<p>I guess the issue of focus may depend on what type of content you are providing. Is it a text that you want the reader to read carefully or just scan? On second thought it may not matter what you as a publisher want. It is all up to the reader I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dragnet Jonas</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13784</link>
		<dc:creator>Dragnet Jonas</dc:creator>
		<pubDate>Wed, 11 Jul 2007 10:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13784</guid>
		<description>It´s fairly easy to split a long text and dynamically create pages if you use asp for example. But I wonder if not a surfer loses his focus if you got a couple of pages instead of gathering all info on one page. Isn´t that a part of the success behind blogs?</description>
		<content:encoded><![CDATA[<p>It´s fairly easy to split a long text and dynamically create pages if you use asp for example. But I wonder if not a surfer loses his focus if you got a couple of pages instead of gathering all info on one page. Isn´t that a part of the success behind blogs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for&#160;2007-07-10&#160;&#124;&#160;David&#8217;s kitchen</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13717</link>
		<dc:creator>links for&#160;2007-07-10&#160;&#124;&#160;David&#8217;s kitchen</dc:creator>
		<pubDate>Tue, 10 Jul 2007 11:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13717</guid>
		<description>[...] Mental Workload for Paged and Scrolled Documents The result showed that mental workload was lower when you read information in a paged way adapted to the screen. Very interesting. (tags: usability design accessibility) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Mental Workload for Paged and Scrolled Documents The result showed that mental workload was lower when you read information in a paged way adapted to the screen. Very interesting. (tags: usability design accessibility) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bookmark: design e interfacce &#124; Marzia Compassi</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13346</link>
		<dc:creator>Bookmark: design e interfacce &#124; Marzia Compassi</dc:creator>
		<pubDate>Fri, 06 Jul 2007 14:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13346</guid>
		<description>[...] da esempi reali per progettare una navigazione di paginazione efficace.Rimanendo in tema, Mental Workload for Paged and Scrolled Documentspresenta uno studio sulla consultabilit di pagine con scrolling o contenuti paginati.Il risultato in [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] da esempi reali per progettare una navigazione di paginazione efficace.Rimanendo in tema, Mental Workload for Paged and Scrolled Documentspresenta uno studio sulla consultabilit di pagine con scrolling o contenuti paginati.Il risultato in [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Stevens</title>
		<link>http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13117</link>
		<dc:creator>Luke Stevens</dc:creator>
		<pubDate>Wed, 04 Jul 2007 04:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.standards-schmandards.com/2007/paged-or-scrolled/#comment-13117</guid>
		<description>IHT.com did this years ago (3 col paged view) as their default view, which was developed by John Weir. Very innovative at the time. You can see a demo of it here: http://www.smokinggun.com/code/sg_layout.php (last updated in 2003), with the source code still available. The IHT eventually dropped the layout for the usual 1 straight col of text, with give-me-more-page-views pagination, and the 3 col view is available as a pop up option. 

Also, in what sense is consumption of information more "efficient" on paper vs screen? Higher comprehension, or higher recall ability or something like that? 

There was also some discussion about the Poynter Institute eye tracking study that suggested readers read more, or at least &lt;a href="http://neilsanderson.com/?p=276" rel="nofollow"&gt;the same amount&lt;/a&gt; of a story online as they do in print, so perhaps it depends on the kind of content &#38; the situation (user motivation, method of reading etc).</description>
		<content:encoded><![CDATA[<p>IHT.com did this years ago (3 col paged view) as their default view, which was developed by John Weir. Very innovative at the time. You can see a demo of it here: <a href="http://www.smokinggun.com/code/sg_layout.php" rel="nofollow">http://www.smokinggun.com/code/sg_layout.php</a> (last updated in 2003), with the source code still available. The IHT eventually dropped the layout for the usual 1 straight col of text, with give-me-more-page-views pagination, and the 3 col view is available as a pop up option. </p>
<p>Also, in what sense is consumption of information more &#8220;efficient&#8221; on paper vs screen? Higher comprehension, or higher recall ability or something like that? </p>
<p>There was also some discussion about the Poynter Institute eye tracking study that suggested readers read more, or at least <a href="http://neilsanderson.com/?p=276" rel="nofollow">the same amount</a> of a story online as they do in print, so perhaps it depends on the kind of content &amp; the situation (user motivation, method of reading etc).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
