<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HCI in Open Source &#187; kpdf</title>
	<atom:link href="http://blog.holehan.org/category/kpdf/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.holehan.org</link>
	<description>It's not bee-log</description>
	<lastBuildDate>Wed, 04 Feb 2009 21:11:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Kpdf usability inspection</title>
		<link>http://blog.holehan.org/2005/04/17/kpdf-usability-inspection/</link>
		<comments>http://blog.holehan.org/2005/04/17/kpdf-usability-inspection/#comments</comments>
		<pubDate>Sun, 17 Apr 2005 14:39:00 +0000</pubDate>
		<dc:creator>Florian Grässle</dc:creator>
				<category><![CDATA[kde]]></category>
		<category><![CDATA[kpdf]]></category>
		<category><![CDATA[openusability]]></category>

		<guid isPermaLink="false">http://blog.holehan.org/?p=3</guid>
		<description><![CDATA[I just finished my first usability inspection on Kpdf. It is a really enjoyable PDF Viewer for KDE. Despite of its -compared to that commercial beast acroread- fairly early state of development KPDF is already quite usable. So the issues that were discovered mainly dealt with naming/wording/sorting of menu and toolbar entries. Another problem I [...]]]></description>
			<content:encoded><![CDATA[<p>I just finished my first usability inspection on <a href=http://kpdf.kde.org>Kpdf</a>. It is a really enjoyable PDF Viewer for KDE. Despite of its -compared to that commercial beast acroread- fairly early state of development KPDF is already quite usable. So the issues that were discovered mainly dealt with naming/wording/sorting of menu and toolbar entries. Another problem I found was the similarity of icons. It is difficult to differentiate &#8220;Previous Page&#8221; from &#8220;Back&#8221; visually if their toolbar icons look the same.</p>
<p>An old notorious friend crossed my path while going through the various actions: the menubar hiding issue. There must be an easy way to recover the menubar in every view/tool/mouse mode apart from &#8220;ctrl+m&#8221;. Otherwise users may feel stupid and blame themselves for losing &#8220;that thing with the names at the top of the window&#8221;. I hope there will be a KDE wide solution for the menubar issue some day, so users can transport the knowledge they gathered from one KDE application to the next.</p>
<p>Now I am looking forward to discussing the findings with the Kpdf developers. It&#8217;s a gift from god for <a href=http://openusability.org> openusability engineers </a> to get involved in software development at such an early stage. Usability engineers of commercial products can usually only dream of that <img src='http://blog.holehan.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.holehan.org/2005/04/17/kpdf-usability-inspection/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

