<?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: Typedia Forms</title>
	<atom:link href="http://www.gettheeye.com/typedia-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gettheeye.com/typedia-forms/</link>
	<description>A series of articles about making software feel good.</description>
	<lastBuildDate>Thu, 22 Jul 2010 14:12:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Zack</title>
		<link>http://www.gettheeye.com/typedia-forms/#comment-30</link>
		<dc:creator>Zack</dc:creator>
		<pubDate>Fri, 28 Aug 2009 23:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettheeye.com/?p=1114#comment-30</guid>
		<description>I&#039;m glad the critique was helpful.  I&#039;m often reluctant to write critiques for fear of offending someone.  

Forms are an often overlooked part of a design, but the difference between a good one and bad one is huge.  I&#039;ve been showing the Typedia edit form to the rest of my team as an example of the type of forms I wish we designed.

Would it be possible to stop unchecking the &quot;This typeface is part of a family&quot; checkbox from clearing the family information?  It could just hide the fields and then show them if the user checked the box again.  You wouldn&#039;t need to delete the family information and it would be there if the user changed their mind.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad the critique was helpful.  I&#8217;m often reluctant to write critiques for fear of offending someone.  </p>
<p>Forms are an often overlooked part of a design, but the difference between a good one and bad one is huge.  I&#8217;ve been showing the Typedia edit form to the rest of my team as an example of the type of forms I wish we designed.</p>
<p>Would it be possible to stop unchecking the &#8220;This typeface is part of a family&#8221; checkbox from clearing the family information?  It could just hide the fields and then show them if the user checked the box again.  You wouldn&#8217;t need to delete the family information and it would be there if the user changed their mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Santa Maria</title>
		<link>http://www.gettheeye.com/typedia-forms/#comment-29</link>
		<dc:creator>Jason Santa Maria</dc:creator>
		<pubDate>Fri, 28 Aug 2009 22:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettheeye.com/?p=1114#comment-29</guid>
		<description>This is a great write-up, definitely well considered and thoughtful. There&#039;s not enough of this happening online, and I thank you for this critique.

The Add/Edit form was easily the most time consuming piece of the site. I plan to post something about the first iteration of it (it&#039;s comical how awful it is by comparison). We labored over this page so much because it&#039;s the most key point of interaction to the site and getting people to participate. I can address a few of your points:

#2 I actually had combined these two in an earlier iteration and the system message helped direct your attention a bit better and strengthen the messaging system. For instance, when you save the page, the page refreshes and the message reads that your changes have been saved. But, you&#039;re still on the Edit page, so the title needs to stay intact as &quot;Edit a typeface&quot;. Having them split gave us much more flexibility.

#3 Yep, we originally had the checkbox as just a normal checkbox, but found that it was actually way too easy to uncheck it by accident and not realize it. So we decided to make it a much more conscious action. And whoops, that warning message should be red like a real warning :)

#5 We didn&#039;t put a resizer on the Background field because most modern browsers have this built into their UI by default now, and it&#039;s one less bit of javascript to include on an already JS heavy page.

#6 The cancel button is an interesting idea. I&#039;ve only heard this from one other person so far. Obviously, I&#039;m so used to the form now that it&#039;s second nature to just trash or erase a field to &quot;cancel&quot; things. I usually tend to avoid placing cancel and reset kinds of buttons in forms because I&#039;m one of those people that always seems to hit them by accident. With all of that said, I&#039;d definitely be interested in ways to improve this form, possibly by conducting some testing with different options.

As I&#039;ve said, this was a very thoughtful critique and I appreciate the time you put into it. I hope you&#039;ll do more too :)</description>
		<content:encoded><![CDATA[<p>This is a great write-up, definitely well considered and thoughtful. There&#8217;s not enough of this happening online, and I thank you for this critique.</p>
<p>The Add/Edit form was easily the most time consuming piece of the site. I plan to post something about the first iteration of it (it&#8217;s comical how awful it is by comparison). We labored over this page so much because it&#8217;s the most key point of interaction to the site and getting people to participate. I can address a few of your points:</p>
<p>#2 I actually had combined these two in an earlier iteration and the system message helped direct your attention a bit better and strengthen the messaging system. For instance, when you save the page, the page refreshes and the message reads that your changes have been saved. But, you&#8217;re still on the Edit page, so the title needs to stay intact as &#8220;Edit a typeface&#8221;. Having them split gave us much more flexibility.</p>
<p>#3 Yep, we originally had the checkbox as just a normal checkbox, but found that it was actually way too easy to uncheck it by accident and not realize it. So we decided to make it a much more conscious action. And whoops, that warning message should be red like a real warning <img src='http://www.gettheeye.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>#5 We didn&#8217;t put a resizer on the Background field because most modern browsers have this built into their UI by default now, and it&#8217;s one less bit of javascript to include on an already JS heavy page.</p>
<p>#6 The cancel button is an interesting idea. I&#8217;ve only heard this from one other person so far. Obviously, I&#8217;m so used to the form now that it&#8217;s second nature to just trash or erase a field to &#8220;cancel&#8221; things. I usually tend to avoid placing cancel and reset kinds of buttons in forms because I&#8217;m one of those people that always seems to hit them by accident. With all of that said, I&#8217;d definitely be interested in ways to improve this form, possibly by conducting some testing with different options.</p>
<p>As I&#8217;ve said, this was a very thoughtful critique and I appreciate the time you put into it. I hope you&#8217;ll do more too <img src='http://www.gettheeye.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
