<?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>The New Interface Advocate &#187; linkedin</title>
	<atom:link href="http://www.hci-matters.com/blog/tag/linkedin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hci-matters.com/blog</link>
	<description>HCI, interface architecture, user experience, and more...</description>
	<lastBuildDate>Sat, 05 Nov 2011 18:53:54 +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>Visualizing Value Distributions and Event Time Clusters in One Dimension (Update:  Source Code Added)</title>
		<link>http://www.hci-matters.com/blog/2011/10/12/archives/289/</link>
		<comments>http://www.hci-matters.com/blog/2011/10/12/archives/289/#comments</comments>
		<pubDate>Wed, 12 Oct 2011 18:47:41 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[information architecture]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[protovis]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[visualization]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=289</guid>
		<description><![CDATA[(Update: The source is available for download at bottom of the entry.) I must admit I always felt a little uncomfortable generating or referencing histograms. The enormous bias that might be introduced by changing the segment/bin size always nags in the back of my mind. True, thoughtfully constructed histograms with a fairly large sample set [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2011/10/12/archives/289/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Flaw in Apple&#8217;s iPad That Defines the Platform</title>
		<link>http://www.hci-matters.com/blog/2011/04/18/archives/258/</link>
		<comments>http://www.hci-matters.com/blog/2011/04/18/archives/258/#comments</comments>
		<pubDate>Mon, 18 Apr 2011 17:41:04 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=258</guid>
		<description><![CDATA[As with most Apple products, the iPad is built from some of the best hardware widely available (depending on your criteria) and has been advertised exceptionally well. In spite of the deluge of predictions that it would change &#8220;everything,&#8221; there seems to be comparatively little deep effect on the tech industry. It feels more like [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2011/04/18/archives/258/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Web Browsing by Gestures (Updated Chrome Fixes)</title>
		<link>http://www.hci-matters.com/blog/2011/03/21/archives/239/</link>
		<comments>http://www.hci-matters.com/blog/2011/03/21/archives/239/#comments</comments>
		<pubDate>Tue, 22 Mar 2011 00:31:11 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Config & Tips]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[linkedin]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=239</guid>
		<description><![CDATA[Web browsers&#8212;despite their diversity of histories, intents, and development paradigms&#8212;largely mirror each other&#8217;s user interfaces with traditional drop-down menus (a.k.a &#8220;File&#8221; menus), either in the standard place or under a top/right corner button, an address/search bar just right of the main navigation button cluster, tabs either above or below it, and the view area below [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2011/03/21/archives/239/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Revised and Expanded RegEx Reference Chart (v2.0)</title>
		<link>http://www.hci-matters.com/blog/2009/08/06/archives/170/</link>
		<comments>http://www.hci-matters.com/blog/2009/08/06/archives/170/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 01:14:05 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Reference]]></category>
		<category><![CDATA[linkedin]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=170</guid>
		<description><![CDATA[I&#8217;ve fixed some minor errors and expanded the languages covered by my RegEx quick reference chart originally posted here: RegEx Reference Chart v1.0. This new version is available in several formats (listed below). Just like the last, it is provided under the Creative Commons Attribution-Share Alike 3.0 License. PDF: Regular Expressions Quick-Reference/Comparison Chart, v2.0 (PDF) [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2009/08/06/archives/170/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Less is More&#8212;Interface Simplification for Vending Machines</title>
		<link>http://www.hci-matters.com/blog/2008/11/12/archives/55/</link>
		<comments>http://www.hci-matters.com/blog/2008/11/12/archives/55/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 12:44:07 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=55</guid>
		<description><![CDATA[Vending machines provide an excellent and disappointingly universal study in overly complex interfaces. This brief post reflects on how the current designs are flawed, speculates on the forces behind the bad designs, and proposes a new design that overcomes current problems though an ultra-minimal interface. Thanks to what appears to be historical inertia, vending machines [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2008/11/12/archives/55/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Lessons from an Etch-a-Sketch&#8212;Implications for HCI</title>
		<link>http://www.hci-matters.com/blog/2008/10/09/archives/50/</link>
		<comments>http://www.hci-matters.com/blog/2008/10/09/archives/50/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 12:51:52 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=50</guid>
		<description><![CDATA[I was in one of Roger Grice&#8217;s HCI courses here at RPI last week, and he showed us the &#8220;interface of the day,&#8221; which was an online simulation of an Etch A Sketch (Etch A Sketch is a trademark of the Ohio Art Company). His point was about the faithfulness it had to the classic [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2008/10/09/archives/50/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Lumiera Timeline First Draft</title>
		<link>http://www.hci-matters.com/blog/2008/05/21/archives/41/</link>
		<comments>http://www.hci-matters.com/blog/2008/05/21/archives/41/#comments</comments>
		<pubDate>Thu, 22 May 2008 05:28:45 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://www.hci-matters.com/blog/?p=41</guid>
		<description><![CDATA[I&#8217;ve pulled together some drafts of my ideas for the design of the timeline portion of the Lumiera non-linear video editor (hopefully, the successor to Cinelerra). The annotated version (explaining some of the finer points): The un-annotated version (to show the sketch better):]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2008/05/21/archives/41/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Search Done Right&#8212;A *Progressive* Progressive Find</title>
		<link>http://www.hci-matters.com/blog/2007/12/30/archives/20/</link>
		<comments>http://www.hci-matters.com/blog/2007/12/30/archives/20/#comments</comments>
		<pubDate>Sun, 30 Dec 2007 19:33:00 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://hci-matters.com/blog/2007/12/30/search-done-right-a-progressive-progressive-find/</guid>
		<description><![CDATA[Edit: I&#8217;ve updated this intro after discovering that I somehow replaced it with some unrevised notes from my initial outline. Oops. I was reading an argument that progressive find is the best (and only proper) search design, I think in the comments of this article. I got to thinking about what makes progressive, and occasionally [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2007/12/30/archives/20/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The only two interface designs ever conceived:</title>
		<link>http://www.hci-matters.com/blog/2007/07/07/archives/16/</link>
		<comments>http://www.hci-matters.com/blog/2007/07/07/archives/16/#comments</comments>
		<pubDate>Sat, 07 Jul 2007 09:55:21 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://hciadvocate.com/blog/?p=16</guid>
		<description><![CDATA[Let&#8217;s see who can guess the two designs I&#8217;m referring to. Here&#8217;s a hint: they&#8217;re more psychological than technical&#8212;and if you say anything involving the words &#8220;GUI,&#8221; &#8220;CLI,&#8221; &#8220;mouse,&#8221; or &#8220;wizard,&#8221; you&#8217;re way off track. The two designs are (drum roll)&#8230; Memorized actions and search. Though I seem to refer to these architectures as a [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2007/07/07/archives/16/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The misused mouse, part 2:  A proposal for a nearly mouseless interface.</title>
		<link>http://www.hci-matters.com/blog/2007/06/16/archives/9/</link>
		<comments>http://www.hci-matters.com/blog/2007/06/16/archives/9/#comments</comments>
		<pubDate>Sat, 16 Jun 2007 14:28:47 +0000</pubDate>
		<dc:creator>R. Clayton Barnes</dc:creator>
				<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[interface architecture]]></category>
		<category><![CDATA[interface design]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://hciadvocate.com/blog/?p=9</guid>
		<description><![CDATA[Since I said the mouse needed to be seriously re-examined as the primary device for interacting with the user-interface (see my previous entry), it&#8217;s only fair that I give an example of a better way to do it. In this entry I explore one possible way to minimally change the interface to almost remove the [...]]]></description>
		<wfw:commentRss>http://www.hci-matters.com/blog/2007/06/16/archives/9/feed/</wfw:commentRss>
		<slash:comments>91</slash:comments>
		</item>
	</channel>
</rss>

