<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>Jon Hartmann - User Interface Design</title>
			<link>http://www.jonhartmann.com/index.cfm</link>
			<description>Technical blog of West Virginia web developer Jon Hartmann, covering ColdFusion, Asp.NET, Javascript, User Interface Design, and current website trends.</description>
			<language>en-us</language>
			<pubDate>Sun, 05 Sep 2010 13:00:07 -0500</pubDate>
			<lastBuildDate>Tue, 05 Jan 2010 11:53:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>jon.hartmann@gmail.com</managingEditor>
			<webMaster>jon.hartmann@gmail.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>jon.hartmann@gmail.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			<itunes:image href="" />
			<image>
				<url></url>
				<title>Jon Hartmann</title>
				<link>http://www.jonhartmann.com/index.cfm</link>
			</image>
			<itunes:explicit></itunes:explicit>
			
			<item>
				<title>UX Videos Article on Smashing Magazine</title>
				<link>http://www.jonhartmann.com/index.cfm/2010/1/5/UX-Videos-Article-on-Smashing-Magazine</link>
				<description>
				
				Check out these &lt;a href=&quot;http://www.smashingmagazine.com/2010/01/05/25-user-experience-videos-that-are-worth-your-time/#more-22480&quot;&gt;videos on User Experiance&lt;/a&gt; at &lt;a href=&quot;http://www.smashingmagazine.com&quot;&gt;Smashing Magazine&lt;/a&gt;. I&apos;ve not had the chance to watch many of them, but there are some gems in there. 
				</description>
				
				<category>User Interface Design</category>				
				
				<pubDate>Tue, 05 Jan 2010 11:53:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2010/1/5/UX-Videos-Article-on-Smashing-Magazine</guid>
				
			</item>
			
			<item>
				<title>Make the Logo Bigger</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/10/13/Make-the-Logo-Bigger</link>
				<description>
				
				Found a very funny song about web design while looking for good articles today. Perhaps it will give you a laugh too, since I found it so sadly familiar. &lt;a href=&quot;http://www.underconsideration.com/speakup/archives/003259.html&quot;&gt;Click here for &apos;Make the Logo Bigger&apos;&lt;/a&gt; (warning, it autoplays). 
				</description>
				
				<category>User Interface Design</category>				
				
				<category>Web Trends</category>				
				
				<pubDate>Tue, 13 Oct 2009 13:18:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/10/13/Make-the-Logo-Bigger</guid>
				
			</item>
			
			<item>
				<title>UX Rule: Fixed Content Width</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/10/7/UX-Rule-Fixed-Content-Width</link>
				<description>
				
				When you&apos;re laying out a site, one of the most basic questions you can ask is &quot;Do we make this liquid or fixed width?&quot; Do you let your site fill the user&apos;s browser, or do you hold it to a single fixed width? It&apos;s a good question, but let me make a suggestion, nay, let me suggestion a &lt;i&gt;rule&lt;/i&gt;: Always use a fixed width for your content.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Wed, 07 Oct 2009 13:56:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/10/7/UX-Rule-Fixed-Content-Width</guid>
				
			</item>
			
			<item>
				<title>Preventing Multiple Submissions with Prototype and jQuery</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/6/11/Preventing-Multiple-Submissions-with-Prototype-and-jQuery</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/javascript.PNG&quot; class=&quot;floatTL&quot; /&gt; If there is one problem that plagues me across applications, its users that are too antsy to wait for the page to come back after hitting submit on a form. Even worse, some people just instinctually double and triple click. How do you keep these pesky users from duplicating records or charging themselves three times for that item in your e-shop? Click &quot;more&quot; to see how I do it in Prototype and jQuery.  [More]
				</description>
				
				<category>Javascript</category>				
				
				<category>jQuery</category>				
				
				<category>Prototype</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Thu, 11 Jun 2009 18:56:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/6/11/Preventing-Multiple-Submissions-with-Prototype-and-jQuery</guid>
				
			</item>
			
			<item>
				<title>Royksopp On Design</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/3/10/Royksopp-On-Design</link>
				<description>
				
				Ok, so not the most serious post, but &lt;a href=&quot;http://twitter.com/cfjedimaster/status/1305757943&quot;&gt;Ray Camden Twittered&lt;/a&gt; about this video, and I have to say that it has some amazing diagrams and charts in it. I can&apos;t help but think that Edward Tufte would like it.

&lt;object width=&quot;500&quot; height=&quot;405&quot;&gt;&lt;param name=&quot;movie&quot; value=&quot;http://www.youtube.com/v/lBvaHZIrt0o&amp;hl=en&amp;fs=1&amp;color1=0x006699&amp;color2=0x54abd6&amp;border=1&quot;&gt;&lt;/param&gt;&lt;param name=&quot;allowFullScreen&quot; value=&quot;true&quot;&gt;&lt;/param&gt;&lt;param name=&quot;allowscriptaccess&quot; value=&quot;always&quot;&gt;&lt;/param&gt;&lt;embed src=&quot;http://www.youtube.com/v/lBvaHZIrt0o&amp;hl=en&amp;fs=1&amp;color1=0x006699&amp;color2=0x54abd6&amp;border=1&quot; type=&quot;application/x-shockwave-flash&quot; allowscriptaccess=&quot;always&quot; allowfullscreen=&quot;true&quot; width=&quot;500&quot; height=&quot;405&quot;&gt;&lt;/embed&gt;&lt;/object&gt; 
				</description>
				
				<category>User Interface Design</category>				
				
				<pubDate>Tue, 10 Mar 2009 15:43:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/3/10/Royksopp-On-Design</guid>
				
			</item>
			
			<item>
				<title>UX Rules: Four Rules for Form Controls</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/2/20/UX-Rules-Four-Rules-for-Form-Controls</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/reset.png&quot; class=&quot;floatTL&quot; alt=&quot;A reset button&quot; /&gt;Time again for another user experience rule, and this time I couldn&apos;t stop at just one. I&apos;ve got four rules for you about forms; one of the most daunting aspects of UX design. You can save yourself some trouble with the following rules:

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Rule 2:&lt;/em&gt; Ditch the Reset button.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 3:&lt;/em&gt; Make your Cancel button look like a link, or make it visually washed out compared to your Submit button.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 4:&lt;/em&gt; Make sure that there is at least a 2em distance between your Submit and your Cancel buttons.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 5:&lt;/em&gt; Submit on the left, Cancel on the right.&lt;p&gt;
&lt;/blockquote&gt;

Read more to see my reasonings and an example.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Fri, 20 Feb 2009 12:46:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/2/20/UX-Rules-Four-Rules-for-Form-Controls</guid>
				
			</item>
			
			<item>
				<title>UX Rule: Notification of Completion</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/2/19/UX-Rule-Notification-of-Completion</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/notifications.PNG&quot; class=&quot;floatTL&quot; alt=&quot;Notification bars&quot; /&gt;

So, as I move into exploring the realm of user experience(UX), I&apos;m going to work on building a collection of rules for creating good user experiences. These rules are fast, but they aren&apos;t hard: every situation is different, and although these rules will be starting points, some negotiation may be required. 

&lt;blockquote&gt;
&lt;em&gt;Rule One:&lt;/em&gt; All processing must display a notification to the user.
&lt;/blockquote&gt;

Read more to see my thoughts on when and how to do this.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Thu, 19 Feb 2009 05:29:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/2/19/UX-Rule-Notification-of-Completion</guid>
				
			</item>
			
			<item>
				<title>Page Layout with Body IDs</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/2/3/Page-Layout-with-Body-IDs</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/html.PNG&quot; alt=&quot;HTML Code Snippet&quot; class=&quot;floatTL&quot; /&gt; A while back I read about a technique to maximize the power of CSS: placing a unique ID on the &amp;lt;body&amp;gt; tag of your markup. Make each page have a unique body ID, and you can use CSS to override anything on that particular page if you want. I&apos;ve played around with this a bit, and found it to be quite powerful technique.&lt;br /&gt;&lt;br /&gt;  [More]
				</description>
				
				<category>User Interface Design</category>				
				
				<pubDate>Tue, 03 Feb 2009 14:23:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/2/3/Page-Layout-with-Body-IDs</guid>
				
			</item>
			
			<item>
				<title>Envisioning Information</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/1/13/Envisioning-Information</link>
				<description>
				
				&lt;a href=&quot;http://www.edwardtufte.com/tufte/&quot;&gt;&lt;img src=&quot;http://www.jonhartmann.com/images/envision_tufte.PNG&quot; alt=&quot;Cover of Envisioning Information by Edward R. Tufte&quot; class=&quot;floatTL&quot;&gt;&lt;/a&gt;

I&apos;d actually ordered this book on Amazon before I read a reference to &lt;a href=&quot;http://www.edwardtufte.com/tufte/&quot;&gt;Edward R. Tufte&lt;/a&gt; in Slide:ology, and so I was immensely happy when I finally got my copy in the mail. Envisioning Information is packed with rich examples of presenting complex, layered data in ways that are usable and even visually pleasing. I recommend this book to any one interested in usability and interface design.

Be warned though, that this book is &lt;em&gt;dense&lt;/em&gt; with ideas, explanations, and images. It reads more like my college biology text book than a normal design book, and the vocabulary is often times as complex. Reading this book can be daunting, but so far, the value I&apos;ve gotten back out of it has been immense.

I think my only complaint about this book is that it is beginning to become dated. Written in 1990, Tufte spends most of his time talking about designs created for printed media, and the examples of computer displays seem very primitive by today&apos;s standards. Luckily, media is no impediment to the concepts in Envisioning Information; &quot;flatland&quot; and &quot;chartjunk&quot; are the same if on a poster or on the web. 
				</description>
				
				<category>Books</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Tue, 13 Jan 2009 15:25:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/1/13/Envisioning-Information</guid>
				
			</item>
			
			<item>
				<title>Slideology</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/1/5/Slideology</link>
				<description>
				
				&lt;a href=&quot;http://blog.duarte.com/&quot;&gt;&lt;img src=&quot;http://www.jonhartmann.com/images/slideology.png&quot; alt=&quot;Cover of Slide:ology by Nancy Duarte&quot; class=&quot;floatTR&quot; target=&quot;_blank&quot; /&gt;&lt;/a&gt;

I&apos;ve fallen in love with &lt;a href=&quot;http://blog.duarte.com/&quot;&gt;Slide:ology&lt;/a&gt; by Nancy Duarte. This book covers just about everything you could want to know about how to design effective slide based presentations. If you have delivered a presentation or ever will deliver one, this book is for you. Whats even better is that even if you&apos;ll never deliver a presentation in your life, then this book might still be for you. 

While focused on presentations, the concepts and insights in Slide:ology are very easily ported to the world of web design: make your point as clearly and simply as possible; images can speak louder then words; colors, fonts, images, everything contributes to the messages you are conveying to your audience. 

Daurte also backs up the guidelines with tons of examples, both in terms of visual ideas to inspire you and in real-world examples of individuals who have employed specific techniques to deliver their message. Give it a spin and see what the world of Power Point can offer web designers. 
				</description>
				
				<category>Conferences and Speaking</category>				
				
				<category>Books</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Mon, 05 Jan 2009 16:52:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/1/5/Slideology</guid>
				
			</item>
			
			<item>
				<title>Why You Must Learn to Love &amp;lt;label&amp;gt;</title>
				<link>http://www.jonhartmann.com/index.cfm/2008/12/4/Why-You-Must-Learn-to-Love-ltlabelgt</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/Html4all-2.png&quot; class=&quot;floatTR&quot; /&gt;

Once you start thinking about usability of internet forms, it starts to really stick in your head. You catch yourself filling out a form and going, &quot;Man, they could probably get more people to fill this out if they just put a line break here, or used a different font color.&quot; Even I, a web developer, tend to shy away from forms that aren&apos;t easy to use, or ask for things I don&apos;t feel like telling them. Maybe thats why I have come to point that I actually get kind of angry when I see people skip out on using the simplest possible usability increaser: the &amp;lt;label&amp;gt; tag.  [More]
				</description>
				
				<category>User Interface Design</category>				
				
				<pubDate>Thu, 04 Dec 2008 22:41:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2008/12/4/Why-You-Must-Learn-to-Love-ltlabelgt</guid>
				
			</item>
			
			<item>
				<title>The Quiet Death of the Major Re-Launch</title>
				<link>http://www.jonhartmann.com/index.cfm/2008/11/30/The-Quiet-Death-of-the-Major-ReLaunch</link>
				<description>
				
				I just saw this cool article on the &lt;a href=&quot;http://www.uie.com/&quot;&gt;User Interface Engineering&lt;/a&gt; website, called &lt;a href=&quot;http://www.uie.com/articles/death_of_relaunch/&quot;&gt;The Quiet Death of the Major Re-Launch&lt;/a&gt;. This article calls out the &quot;big relaunch&quot; as being a potential pain point with users, and I have to agree whole heartedly. It doesn&apos;t really mention it in the article, but I think incremental role out of new features can also help to make realistic expectations for the results of updates. Its hard to get over hyped about updates to a single navigation menu. It also doesn&apos;t say that this is the perfect way to find out what changes are increasing your conversion rate; implementing one change at a time over a period of weeks lets you know which change is having an impact, and how. 
				</description>
				
				<category>Conversion and SEO</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Sun, 30 Nov 2008 17:14:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2008/11/30/The-Quiet-Death-of-the-Major-ReLaunch</guid>
				
			</item>
			
			<item>
				<title>Designing the Moment</title>
				<link>http://www.jonhartmann.com/index.cfm/2008/11/30/Designing-the-Moment</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/design.PNG&quot; class=&quot;floatTL&quot; alt=&quot;Cover of Designing the Moment by Rober Hoekman, Jr.&quot;&gt;

I&apos;ve finished reading &lt;a href=&quot;http://www.amazon.com/Designing-Moment-Interface-Design-Concepts/dp/0321535081&quot;&gt;Designing the Moment&lt;/a&gt; by&lt;a href=&quot;http://rhjr.net/&quot;&gt;Robert Hoekman, Jr.&lt;/a&gt;, and it was an excellent book to follow up Web Design for ROI. I&apos;d read Robert&apos;s other book, Designing the Obvious as well, and this book is no less impressive. Since I spend most of my time in back-end developer land, its awesome to read books which offer not only great advice, but great advice that says that the user experience flows from the beginning to the end of the project; its not the job of just a front end developer or designer.

Check it out for great advice on how to analyze your apps to make them more usable, and thus increase conversions. 
				</description>
				
				<category>Books</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Sun, 30 Nov 2008 16:47:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2008/11/30/Designing-the-Moment</guid>
				
			</item>
			
			<item>
				<title>BlogCFC Tweaks: Easier Category Selection</title>
				<link>http://www.jonhartmann.com/index.cfm/2008/11/29/BlogCFC-Tweaks-Easier-Category-Selection</link>
				<description>
				
				I&apos;ve talked about it before, but I find classic multi-selects in HTML to be really hard to use. You invariably have to end up putting some explanation text to let a user know how to select more then one, and its easy to clear your selections everything while trying to select an additional item. I put these ideas into practice in BlogCFC to help with category selection. I replaced the following code in admin/entry.cfm starting at line 391:

&lt;code&gt;&lt;cfif allCats.recordCount&gt;
	&lt;select name=&quot;categories&quot; multiple size=4 class=&quot;txtDropdown&quot;&gt;
	&lt;cfloop query=&quot;allCats&quot;&gt;
		&lt;option value=&quot;#categoryID#&quot; &lt;cfif isDefined(&quot;form.categories&quot;) and listFind(form.categories,categoryID)&gt;selected&lt;/cfif&gt;&gt;#categoryName#&lt;/option&gt;
	&lt;/cfloop&gt;
	&lt;/select&gt;&lt;br&gt;
&lt;/cfif&gt;&lt;/code&gt;

With this code:

&lt;code&gt;&lt;cfif allCats.recordCount&gt;
	&lt;ul class=&quot;multiselect&quot;&gt;
		&lt;cfloop query=&quot;allCats&quot;&gt;
			&lt;li&gt;&lt;input id=&quot;cat_#categoryID#&quot; type=&quot;checkbox&quot; name=&quot;categories&quot; value=&quot;#categoryID#&quot;&lt;cfif isDefined(&quot;form.categories&quot;) and listFind(form.categories,categoryID)&gt; checked=&quot;checked&quot;&lt;/cfif&gt;/&gt;&lt;label for=&quot;cat_#categoryID#&quot;&gt;#categoryName#&lt;/label&gt;&lt;/li&gt;
		&lt;/cfloop&gt;
	&lt;/ul&gt;
&lt;/cfif&gt;&lt;/code&gt;

I also added the following code the admin style sheet ( /includes/admin.css ):

&lt;code&gt;
ul.multiselect {
	height: 100px; 
	width: 225px; 
	border: 1px solid silver; 
	list-style-type: none; 
	padding-left: 3px; 
	overflow: auto;
}
ul.multiselect li label {
	display: inline;
	padding-left: 2px;
}&lt;/code&gt;

That makes it a lot easier to keep track of categories without messing something up. 
				</description>
				
				<category>BlogCFC</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Sat, 29 Nov 2008 05:30:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2008/11/29/BlogCFC-Tweaks-Easier-Category-Selection</guid>
				
			</item>
			
			<item>
				<title>My first Webkit and FireFox 3 standards let down</title>
				<link>http://www.jonhartmann.com/index.cfm/2008/11/3/My-first-Webkit-and-FireFox-3-standards-let-down</link>
				<description>
				
				So today I finally found a part of the HTML 4.01 standard that Internet Explorer 6 (and 7) follows better then FireFox 3 and Webkit: &amp;lt;colgroup&amp;gt; and lt;col&amp;gt; tags. Apparently, neither FF3 or Webkit (and thus Chrome) bother to implement these tags. Normally, FF3 and Webkit are on the right side of standards, so its kind of a disappointment, especially when I need the functionality of those tags for a project.

If you aren&apos;t familiar with them, browse on over to &lt;a href=&quot;http://www.w3schools.com/tags/default.asp&quot;&gt;W3School&apos;s XHTML reference&lt;/a&gt; and get acquainted. Basically, with column groups you can implement nice things like setting a column&apos;s background color without adding classes to each lt;td&amp;gt; in that column.

I hope that FF3 and Webkit see there way to implementing this feature. 
				</description>
				
				<category>User Interface Design</category>				
				
				<pubDate>Mon, 03 Nov 2008 11:05:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2008/11/3/My-first-Webkit-and-FireFox-3-standards-let-down</guid>
				
			</item>
			</channel></rss>