<?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: Standardizing web forms</title>
	<atom:link href="http://www.usercore.com/2007/05/09/standardizing-web-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usercore.com/2007/05/09/standardizing-web-forms/</link>
	<description>Matt MacDougall - attempting to grok users, management, marketing, linux, subversion, coldfusion, os x and web geekery</description>
	<pubDate>Wed, 20 Aug 2008 17:25:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Dragan Babic</title>
		<link>http://www.usercore.com/2007/05/09/standardizing-web-forms/#comment-5</link>
		<dc:creator>Dragan Babic</dc:creator>
		<pubDate>Thu, 31 May 2007 18:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.usercore.com/2007/05/09/standardizing-web-forms/#comment-5</guid>
		<description>Hi guys, first of all thanks for taking interest in Uni-Form. Now to answer some of your questions: 

@Michael Long: 

1) The design doesn't imply anything, although it is correct that it gets tricky when you need a complex form. Consider Uni-Form's default units as something to get you started and that will make the work easier for you, but don't let it set you any boundaries or limitations, you still need to use your creativity to achieve wanted results. As far as multiple inputs per line go, please check out this thread that deals with that exclusively http://dnevnikeklektika.com/uni-form/community/discussion/15/layout-tip-stack-your-fields-with-col/. 

2) What you are talking about is the current default styling, and it is just a matter of preference in most cases. I usually deal with those issues (field lengths) by adding additional classes, or giving the control of the width of the field to the length attribute (or rows and cols in the case of textareas). 

Cheers.</description>
		<content:encoded><![CDATA[<p>Hi guys, first of all thanks for taking interest in Uni-Form. Now to answer some of your questions: </p>
<p>@Michael Long: </p>
<p>1) The design doesn&#8217;t imply anything, although it is correct that it gets tricky when you need a complex form. Consider Uni-Form&#8217;s default units as something to get you started and that will make the work easier for you, but don&#8217;t let it set you any boundaries or limitations, you still need to use your creativity to achieve wanted results. As far as multiple inputs per line go, please check out this thread that deals with that exclusively <a href="http://dnevnikeklektika.com/uni-form/community/discussion/15/layout-tip-stack-your-fields-with-col/" rel="nofollow">http://dnevnikeklektika.com/uni-form/community/discussion/15/layout-tip-stack-your-fields-with-col/</a>. </p>
<p>2) What you are talking about is the current default styling, and it is just a matter of preference in most cases. I usually deal with those issues (field lengths) by adding additional classes, or giving the control of the width of the field to the length attribute (or rows and cols in the case of textareas). </p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Long</title>
		<link>http://www.usercore.com/2007/05/09/standardizing-web-forms/#comment-6</link>
		<dc:creator>Michael Long</dc:creator>
		<pubDate>Mon, 28 May 2007 18:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.usercore.com/2007/05/09/standardizing-web-forms/#comment-6</guid>
		<description>I have  two main issues with the uni-form sample given:

1) The design wants a single form field per line. This precludes standard conventions like city / state / zip and as such makes the form appear much longer to the user. Users don't like long forms.

2) As styled, the every-field-is-the-same-length design may &#34;look&#34; more appealiing to some, but in doing so it stops giving useful hints to the user about the size of expected responses. (e.g. a very narrow &#34;state&#34; field reinforces the fact that we'd prefer the abbreviation and not the entire name) 

CSS-based forms also have issues when used under older browsers (as do most things), which may be a problem depending upon your user base.</description>
		<content:encoded><![CDATA[<p>I have  two main issues with the uni-form sample given:</p>
<p>1) The design wants a single form field per line. This precludes standard conventions like city / state / zip and as such makes the form appear much longer to the user. Users don&#8217;t like long forms.</p>
<p>2) As styled, the every-field-is-the-same-length design may &quot;look&quot; more appealiing to some, but in doing so it stops giving useful hints to the user about the size of expected responses. (e.g. a very narrow &quot;state&quot; field reinforces the fact that we&#8217;d prefer the abbreviation and not the entire name) </p>
<p>CSS-based forms also have issues when used under older browsers (as do most things), which may be a problem depending upon your user base.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
