<?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>Simfatic Solutions Blog</title>
	<atom:link href="http://www.simfatic.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.simfatic.com/blog</link>
	<description>Updates on Simfatic Solutions</description>
	<lastBuildDate>Sat, 24 Jul 2010 15:49:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to add a &#8216;Confirm Email&#8217; field</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/220/add-a-confirm-email-field/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/220/add-a-confirm-email-field/#comments</comments>
		<pubDate>Sat, 24 Jul 2010 15:47:00 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[HowTo's]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=220</guid>
		<description><![CDATA[It is common to have a validation that compares two fields in the form &#8211; Confirm Password, Confirm email and so on. Some developers believe that this will ensure that the correct email/password is entered. Just like you, I also don&#8217;t like typing my email twice; but, since you asked, here is how to do [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/confirm-email-form.png" alt="Confirm Email Field" width="342" height="164" class="size-full wp-image-223" /></p>
<p>It is common to have a validation that compares two fields in the form &#8211; Confirm Password, Confirm email and so on. </p>
<p>Some developers believe that this will ensure that the correct email/password is entered. Just like you,  I also don&#8217;t like typing my email twice; but, since you asked, here is how to do it in Simfatic Forms.<br />
<span id="more-220"></span></p>
<p>First, add the email field and the &#8216;confirm email&#8217; fields to your form.</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/drop-email-confirm-field.png" alt="Confirm Email Field" width="519" height="277" class="size-full wp-image-224" /></p>
<p>Proceed to the &#8216;Input Validations&#8217; page. </p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/confirm-email-validation.png" alt="Select the &#039;compare&#039; validation" width="558" height="323" class="alignnone size-full wp-image-225" /></p>
<p>Select the ConfirmEmail field on the left side<br />
Select the &#8216;Comparisons&#8217; tab on the right side.<br />
Press the &#8216;Add&#8217; button.</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/add-confirm-email-validation.png" alt="Add the comparison validation" width="589" height="329" class="alignnone size-full wp-image-226" /></p>
<p>Select &#8216;Equal To&#8217; and choose the &#8216;Email&#8217; field</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/confirm-email-validation-err.png" alt="Edit the validation error string" width="572" height="241" class="alignnone size-full wp-image-227" /><br />
You may also like to change the error string.<br />
Select the &#8220;=Email&#8221; validation node and update the error string.</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/confirm-email-testing.png" alt="Testing the Confirm email validation" width="512" height="123" class="alignnone size-full wp-image-230" /></p>
<p>Done!</p>
<p>Note that the comparison validations can be extended further (like a &lt; b &gt; y) </p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/220/add-a-confirm-email-field/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>New Release: Simfatic Forms 3.1.4</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/200/new-release-simfatic-forms-314/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/200/new-release-simfatic-forms-314/#comments</comments>
		<pubDate>Thu, 15 Jul 2010 13:13:18 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[new release]]></category>
		<category><![CDATA[Simatic Forms]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=200</guid>
		<description><![CDATA[A new release of Simfatic Forms is available for download. This new release primarily contains bug fixes and improvements. Here is a brief list of improvements in this new update: Fixed the date validation problem where some dates where accepted in the client side; but not on the server side Fixed issues that used to [...]]]></description>
			<content:encoded><![CDATA[<p>A new release of Simfatic Forms is available for download. This new release primarily contains bug fixes and improvements.</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/simfatic-screenshot-3-1-4.png" alt="simfatic-screenshot-3-1-4" width="589" height="384" class="alignnone size-full wp-image-203" /><br />
<span id="more-200"></span><br />
Here is a brief list of improvements in this new update:</p>
<ol>
<li>Fixed the date validation problem where some dates where accepted in the<br />
client side; but not on the server side</li>
<li>Fixed issues that used to occur with large forms (with many fields)</li>
<li>Some more minor fixes and improvements</li>
</ol>
<p><a href="http://www.simfatic.com/downloads/simfatic-forms.exe">Download Simfatic Forms 3.1.4</a></p>
<p><strong>Some recent feedback on Simfatic Forms :</strong></p>
<blockquote><p>&#8220;I love this program! Why? It took me hours of coding before I tried the demo version of Simfatic Forms. Now I it takes me no time to make the exact forms I need.<br />
Also, the support is great and fast.<br />
Thanks for saving me hours of work! &#8221;</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/brian5.jpg" alt="brian5" width="107" height="146" class="alignnone size-full wp-image-207" /><br />
Brian Poedenphant<br />
<a href="http://www.experien.dk">http://www.experien.dk</a>
</p></blockquote>
<p>
&#8220;For reasons mainly of security and user-reassurance, I needed a quick replacement for an existing Flash-based form. It had to work over SSL and have file upload, email notification and Captcha (or similar) anti-bot functionality.</p>
<p>I&#8217;m not a techie-whiz by any means, but I got the new form completed, debugged, tested and deployed within 3 hours of first coming across Simfatic on a web search. Nothing fancy &#8211; just solid functionality as can be seen at the URL below&#8221;</p>
<p>Webmaster,<br />
<a href="https://wikispooks.com">https://wikispooks.com</a>
</p>
<blockquote><p>&#8220;I was a little skeptical at first that a form development tool would be robust enough to really help me create forms and integrate them into the dynamic websites I build.</p>
<p>I quickly discovered that Simfatic Forms really is Simply Fantastic, as they say in their logo. It took me almost a half day to do my first form while I learned the tool, and during that time had to send a couple of questions in that they quickly answered. Now that I have created several form templates, the tasks of developing a form, validation, and processing that used to take me hours is finished in a fraction of the time, and the forms look great.</p>
<p>I just wish that I had this tool sooner! &#8221;</p>
<p>Terrye Hoffman ,<br />
Prairie Skies Technical Services, LLC
</p></blockquote>
<p>
&#8220;Powerful feedback forms and easy to build. Step by step instructions. Suitable for someone like me with small knowledge in website building. Very quick response from Simfatic Solutions support team. &#8221;</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2010/07/christopher-finland.jpg" alt="christopher-finland" width="106" height="116" class="alignnone size-full wp-image-211" /><br />
Christopher Finland<br />
<a href="http://www.pitopalvelu-vassallo.com/">http://www.pitopalvelu-vassallo.com/</a>
</p>
<p>Thanks for the encouraging feedback guys!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/200/new-release-simfatic-forms-314/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Simfatic Forms 3.1 released!</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/184/simfatic-forms-31-released/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/184/simfatic-forms-31-released/#comments</comments>
		<pubDate>Fri, 16 Apr 2010 14:25:39 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[new release]]></category>
		<category><![CDATA[Simfatic Forms 3.1]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=184</guid>
		<description><![CDATA[Simfatic Forms 3.1 is finally out of beta. There are a number of enhancements available in this new update. Here is the summary: 1. You can change the DocType of generated code in Options &#38; Settings 2. The generated code passes HTML/XHTML(strict) validations at w3.org 3. More standardization: &#8216;label&#8217; tag and &#8216;for&#8217; attribute 4. CSS [...]]]></description>
			<content:encoded><![CDATA[<p>Simfatic Forms 3.1 is finally out of beta. </p>
<p>There are a number of enhancements available in this new update. </p>
<p>
Here is the summary:</p>
<p>
1. You can change the DocType of generated code in Options &amp; Settings</p>
<p>2. The generated code passes HTML/XHTML(strict) validations at w3.org</p>
<p>3. More standardization: &#8216;label&#8217; tag and &#8216;for&#8217; attribute<br />
<span id="more-184"></span><br />
4. CSS positioning in separate CSS file rather than inline style</p>
<p>5. The position and size of the elements could be adjusted precisely.<br />
   There are edit boxes in the &#8216;Draw the form&#8217; page to adjust the size and position of the elements.<br />
   The form size also could be adjusted.</p>
<p>6. Print button in &#8216;confirm&#8217; page. The buttons in &#8216;Confirm&#8217; page can be adjusted individually.</p>
<p>7. CAPTCHA can have i18n (non-English) characters &amp; CAPTCHA case insensitive option</p>
<p>8. New &#8216;automatic&#8217; variables: User Agent, Referrer Page, O.S, Browser ,Form submission date</p>
<p>9. HTTP authentication is supported.</p>
<p>10. Better Form templates. Form templates can now be shared</p>
<p>11. &#8216;Extension Modules&#8217; for extending the default functionality</p>
<p>12. Many other fixes and improvements<br />
</P>
</p>
<p>
Thank you very much for all the beta participants for reporting the issues you found and for the wonderful suggestions. You will soon get the email containing the free license.</p>
<p>
Here is the best part: <strong>the upgrade is free for all Simfatic Forms 3.0 customers!</strong><br />
The existing license keys will work fine with the new version.
</p>
<p>
<a href='http://www.simfatic.com/forms/download.php'>Go here to download Simfatic Forms 3.1</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/184/simfatic-forms-31-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release: Simfatic Forms 3.1 Beta 2</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/164/new-release-simfatic-forms-31-beta-2/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/164/new-release-simfatic-forms-31-beta-2/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 17:22:00 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[new release]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=164</guid>
		<description><![CDATA[A new version of Simfatic Forms 3.1 Beta is available for download. This release contains several fixes and enhancements over beta 1. Before going into the details of the release, let me thank you for the overwhelming feedback Those comments really shape Simfatic Forms. I have to admit that only those suggestions that can be [...]]]></description>
			<content:encoded><![CDATA[<p>A new version of Simfatic Forms 3.1 Beta is available for <a href="http://www.simfatic.com/forms/download-beta.php">download</a>. This release contains several fixes and enhancements over beta 1.<br />
<span id="more-164"></span><br />
<img src="http://www.simfatic.com/blog/wp-content/uploads/2010/03/simfatic-forms-extension1.png" alt="Simfatic Forms 3.1 beta Extension Module Page" width="567" height="363" class="alignnone size-full wp-image-177" /></p>
<p>Before going into the details of the release,  let me thank you for the overwhelming feedback <img src='http://www.simfatic.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   Those comments really shape Simfatic Forms.</p>
<p>I have to admit that only those suggestions that can be included in the scope of this intermediate version got into this release.  But, rest assured, the remaining will be taken up in version 4.0.</p>
<p>Simfatic Forms 3.1 will be taken out of beta <em>very</em> soon so that the complete effort is concentrated on Version 4.0 of Simfatic Forms. </p>
<p>Here are the major changes in this new release:</p>
<ol>
<li>adds comment header on the top of the generated PHP page</li>
<li>Proper label for group elements (radio/checkbox) </li>
<li>CAPTCHA case insensitive option</li>
<li>Fixed a problem with email encoding (observed on some servers)</li>
<li>Many other minor fixes and improvements</li>
</ol>
<p>Here is the link to the download<br />
<a href="http://www.simfatic.com/forms/download-beta.php">Simfatic Forms 3.1 Beta</a></p>
<p>Keep <a href="http://www.simfatic.com/report-bug.phtml">posting your feedback</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/164/new-release-simfatic-forms-31-beta-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release: Simfatic Forms 3.1 Beta</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/148/new-release-simfatic-forms-31-beta/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/148/new-release-simfatic-forms-31-beta/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 11:18:33 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[create web form]]></category>
		<category><![CDATA[form maker]]></category>
		<category><![CDATA[Simfatic Forms beta]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=148</guid>
		<description><![CDATA[Simfatic Forms 3.1 comes with a set of &#8216;high demand&#8217; features. The next version (Simfatic Forms 4.0) will address almost all feature requests that you had requested. However, it will take a few months to complete all of them. Meanwhile, it looks like a good idea to have an intermediate version with the most demanded [...]]]></description>
			<content:encoded><![CDATA[<p>Simfatic Forms 3.1 comes with a set of &#8216;high demand&#8217; features. </p>
<p>The next version (Simfatic Forms 4.0) will address almost all feature requests that you had requested. However, it will take a few months to complete all of them. Meanwhile, it looks like a good idea to have an intermediate version with the most demanded features.<br />
<span id="more-148"></span><br />
<img src="http://www.simfatic.com/blog/wp-content/uploads/2010/02/simfatic-forms31.png" alt="Simfatic Forms 3.1 Beta" width="513" height="342" class="size-full wp-image-158" /></p>
<p>Here are the highlights of Simfatic Forms 3.1 </p>
<ul>
<li>Ability to adjust the Position and size of the form elements precisely in pixel values.</li>
<li>Generates HTML/XHTML strict code. (You can get the code validated 100% at validator.w3.org)</li>
<li>Ability to extend the functionality of Simfatic Forms through your own &#8216;Extension Modules&#8217;</li>
</ul>
<p><a href='http://www.simfatic.com/forms/download-beta.php'>See this page for more details</a></p>
<p>Go ahead and try the new Simfatic Forms. As always, <strong>all active Beta participants will get free Simfatic Forms licenses</strong>.</p>
<p>Take care of a few things though:</p>
<ul>
<li>Use this Beta version for testing only </li>
<li>Before opening existing form designs (the fwz file), take a backup of the file</li>
</ul>
<p>Get your copy of Simfatic Forms 3.1 beta from the page below:<br />
<a href='http://www.simfatic.com/forms/download-beta.php'>Simfatic Forms 3.1 Beta</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/148/new-release-simfatic-forms-31-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simfatic Forms Release 3.0.5</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/141/simfatic-forms-release-305/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/141/simfatic-forms-release-305/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 11:52:38 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=141</guid>
		<description><![CDATA[An updated version of Simfatic Forms is available for download. This update includes minor fixes and some improvements. Here are the major changes: 1. Fixed a problem in the calculation field script (List box/radio button value not counted properly in the calculation) 2. Applied CodeSign Certificate 3. Fixed problem with date field validations (Date validations [...]]]></description>
			<content:encoded><![CDATA[<p>An updated version of Simfatic Forms is available for download. This update includes minor fixes and some improvements.<br />
<span id="more-141"></span><br />
Here are the major changes:<br />
1. Fixed a problem in the calculation field script<br />
(List box/radio button value not counted properly in the calculation)</p>
<p>2. Applied CodeSign Certificate</p>
<p>3. Fixed problem with date field validations<br />
(Date validations were applied even if the field was empty)</p>
<p>4. Troubleshooting help link for &#8216;No email&#8217; cases.<br />
(A link is added to help troubleshoot &#8216;No email received&#8217; cases)</p>
<p><a href="http://www.simfatic.com/forms/new-updates.php">Download Simfatic Forms Here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/141/simfatic-forms-release-305/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Evolving your form</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/#comments</comments>
		<pubDate>Sat, 03 Oct 2009 11:23:09 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[form design]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=116</guid>
		<description><![CDATA[Some of the recent support requests made me think of this: how to make building complex forms easier? If you have used Simfatic Forms, you will immediately realize that Simfatic Forms makes it pretty quick to build a large form. Taken by this, users build a large form and get overwhelmed by the large set [...]]]></description>
			<content:encoded><![CDATA[<p>Some of the recent support requests made me think of this: how to make building complex forms easier? If you have used Simfatic Forms, you will immediately realize that Simfatic Forms makes it pretty quick to build a large form. Taken by this, users build a large form and get overwhelmed by the large set of input fields that they have to deal with in the later steps.</p>
<p>Here is how to develop your (big or small) form iteratively. The iterative approach is guaranteed to take half the complexity away.<br />
<span id="more-116"></span></p>
<h2>Start from a simple form</h2>
<p>Add the minimum number of fields to the form. Simfatic Forms provides you the flexibility of updating the form at any later point. So don&#8217;t worry about having the perfect form design in the first step itself.</p>
<h2>Designing calculation fields  or  validations without uploading the form</h2>
<p>The client side validations and calculation fields can be tested before installing the form on the webserver. One option is to use the preview feature. </p>
<p>Yet another option is to start with a &#8216;client side only&#8217; form first and add the server side options later. Here is how to do it:<br />
In the &#8216;Form General&#8217; page, in the &#8216;Form Processing&#8217; tab, choose the &#8216;Other&#8217; option for &#8216;Server side processing&#8217;. Leave the &#8216;action&#8217; field empty.<br />
<img src="http://www.simfatic.com/blog/wp-content/uploads/2009/09/general-form-props.png" alt="general-form-props" width="473" height="219" class="alignnone size-full wp-image-123" /><br />
Now you can preview the form in your browser (locally) as you develop the form ( Proceed to the &#8216;Generate Code&#8217; page and press the &#8216;Open the form&#8217; button.)</p>
<p>This &#8216;Client side first&#8217; method is best for forms with complex calculation fields or those with complex validations. You can build and test the form without installing the form on the web server each time.</p>
<p>Once the form design is ready, choose the &#8216;Simfatic Forms&#8217; form processor&#8217; option ( in the &#8216;Form processing options&#8217; tab) and proceed with designing the server side options.</p>
<h2>Choose the minimum options, install it and get the form running</h2>
<p>In the &#8216;form processing options&#8217; page choose one of the options ( like &#8216;send form submission by email&#8217; or &#8216;confirmation page&#8217; ) , install the form and see the form working. </p>
<h2>Iterate; add more fields and test again</h2>
<p>Now add more fields and more server side options. Make sure that the auto-generated templates (like the email template) are generated again. Re-install the form. Test the form again.</p>
<p>During the further iterations you can add more complexity: like adding a calculation field, changing the style of the form (the &#8216;look and feel page&#8217;) , saving to database and more.</p>
<h2>Keeping backups of your form design</h2>
<p>The form design you make using Simfatic Forms can be saved to an .fwz file (choose the file-&gt;Save menu item). It can often happen that after making some design changes you originally liked an earlier one. It is always good to keep intermittent backups of work in progress. This way if you want to roll back to an older design quickly.<br />
(This is true for any work in progress &#8211; like a document in progress or even a web page design in progress)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Before putting CAPTCHA on your next web form</title>
		<link>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/</link>
		<comments>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 11:33:45 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Web Forms]]></category>
		<category><![CDATA[captcha]]></category>
		<category><![CDATA[form design]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=82</guid>
		<description><![CDATA[CAPTCHA has become common part in almost any web form now-a-days. It has become increasingly difficult to decipher the code even for extra-ordinary humans ! There are several discussions on the usability issues of CAPTCHA (here are some more). A bad CAPTCHA can bring down the number of form submissions considerably. You may lose leads, [...]]]></description>
			<content:encoded><![CDATA[<p><a href='http://en.wikipedia.org/wiki/CAPTCHA'>CAPTCHA</a> has become common part in almost any web form now-a-days. It has become increasingly difficult to decipher the code even for extra-ordinary humans ! </p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-sample1.png" alt="captcha-sample" width="309" height="168" class="alignnone size-full wp-image-95" /><br />
<span id="more-82"></span><br />
There are several discussions on the <a href='http://blog.akismet.com/2009/02/04/make-commenting-easy/'>usability issues of CAPTCHA</a> (here are <a href='http://www.sitepoint.com/blogs/2008/06/18/reddits-flawed-captcha-adding-insult-to-injury/'>some</a> <a href='http://designbit.co.uk/2009/07/07/i-hate-captchas/'>more</a>). A bad CAPTCHA can <a href='http://www.seomoz.org/blog/captchas-affect-on-conversion-rates'>bring down the number of form submissions considerably</a>. You may lose leads, business, or contacts just because of an inappropriate CAPTCHA.</p>
<p>Let&#8217;s see when to use CAPTCHA (importantly, when <strong>not</strong> to use) and if at all required, how to make it easier for your visitors.</p>
<h2>Why CAPTCHA at all?</h2>
<p>CAPTCHA is for preventing bots from automatically submitting your form. These web bots are programs that leech through the web pages. When it finds a form, it fills the form with a spam message and submits.</p>
<p><strong>Why would someone send a web-bot to submit your form? What is their gain?</strong></p>
<ol>
<li>If the form submission appears immediately on a web page, the spammer can get back links to his website</li>
<p>The examples include blog comment forms and guest books. It is important that no form submission appears immediately on a web page. It will be an open invitation to spammers. Put a monitoring system in place.</p>
<li>If you are providing a free service (free email, free blogs) the spammer can create several thousand accounts</li>
<li>The spammer expects <em>you</em> to read his spam message</li>
<p>Rest of the forms fall in the third category. This category is the least attractive to the spammer since only you see the spam message! The chances of spam submissions to this category is the least. So why bother about CAPTCHA itself?
</ol>
<h2>Does your form really need a CAPTCHA?</h2>
<p>There is no reason to attach a CAPTCHA with every form that you get online. </p>
<ol>
<li>Design the form without CAPTCHA. Get it online!</li>
<li>You start getting form submissions. Take a note of the number of form submissions. (the conversion rate)</li>
<li> If you start getting spam submissions, attach a CAPTCHA.</li>
<li> Observe the drop in the number of genuine form submissions. Decide whether to keep the CAPTCHA </li>
</ol>
<p>If you have decided to keep the CAPTCHA, try the tips below to keep it easier for your visitors.</p>
<h2>Making a better CAPTCHA</h2>
<p>A good CAPTCHA will keep the form submission rate high while keeping the bots away. </p>
<div class='Para2'>
<h3>1. Avoid similar symbols in the CAPTCHA</h3>
<p>There are several characters that look similar. CAPTCHA, by nature is distorted. The similarity can cause confusion.</p>
<p>Examples:<br />
1(one) l(lowercase L) and I (uppercase i)<br />
0(zero) and O and o (lowercase O)<br />
4 and A<br />
8 and B<br />
6 and b</p>
<h3>2. Password field for Captcha?</h3>
<p>I don&#8217;t understand why some web forms have *Password field* for filling in the captcha code!</p>
<p>Password field, supposedly, is to prevent someone  seeing the entered text &#8216;over your shoulder&#8217;; right?</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-pwd.png" alt="captcha with password field" width="462" height="172" class="alignnone size-full wp-image-86" /></p>
<h3>3. Fill the form again? Oh No!</h3>
<p>Though this is very basic, I have seen this happening at least in a couple of forms.<br />
You fill the form, and manage to fill the CAPTCHA and submit. Bang! The form appears again and says the CAPTCHA code is wrong. That&#8217;s fine; but the entire form is cleared too!<br />
Use Ajax to validate CAPTCHA; never make the visitor fill the form again.</p>
<h3>4. Make it bigger</h3>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-small.png" alt="too small captcha" width="303" height="117" class="alignnone size-full wp-image-87" /><br />
Bigger text is easier to decipher. The size of the characters doesn&#8217;t matter for the bots anyway. So make it larger.</p>
<h3>5. No Fancy fonts please!</h3>
<p>It is easier to decipher the code if the font is a familiar one.  Use a common, non-fancy font in the CAPTCHA</p>
<h3>6. Link to refresh the CAPTCHA.</h3>
<p>Always give an option to refresh the CAPTCHA. In case one code is difficult, your visitors can try another one.</p>
<h3>7. Keep it short</h3>
<p>A 6 character CAPTCHA code is reasonable while anything more than 10 is too much!
</p></div>
<p>Use CAPTCHA only when necessary. Even if you decided to have CAPTCHA, make it easier for your visitors.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>After the &#8216;Big&#8217; Release</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/72/after-the-big-release/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/72/after-the-big-release/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 12:26:02 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[simfatic forms release]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=72</guid>
		<description><![CDATA[It has been one week after the release of Simfatic Forms 3.0. It was for sure a busy week. Beta Participants The free licenses for all Beta participants were sent out. There were 140 active beta participants for Simfatic Forms 3.0. ( that is $13,860 worth of licenses! ) If you participated in the beta [...]]]></description>
			<content:encoded><![CDATA[<p>It has been one week after the release of Simfatic Forms 3.0. It was for sure a busy week.<br />
<span id="more-72"></span></p>
<h3>Beta Participants</h3>
<p>The free licenses for all Beta participants were sent out. There were <b>140</b> active beta participants for Simfatic Forms 3.0. ( that is <b>$13,860</b> worth of licenses! )</p>
<p>
If you participated in the beta program and didn&#8217;t get my email for some reason, please contact me for your free license.
</p>
<h3>Existing Customers</h3>
<p>I sent out an email announcement to all existing Simfatic Forms customers as well. The email contains information on how to upgrade to Simfatic Forms 3.0</p>
<h3>Web site updates</h3>
<p><a href='http://www.simfatic.com'>Simfatic.com</a> website went through a major revamp as part of releasing Simfatic Forms 3.0</p>
<p>There are still some more fine tuning in progress.</p>
<p>If you spot a JavaScript error or a typo, let me know.</p>
<p>I would also appreciate your feedback on the <a href='/forms/benefits.php'>updated web site</a>.</p>
<p><a href='/report-bug.phtml'>Feedback form</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/72/after-the-big-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>End of Beta and a humble invitation to Bloggers</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/60/invitation-to-bloggers/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/60/invitation-to-bloggers/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 16:59:33 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[blogger]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=60</guid>
		<description><![CDATA[Simfatic Forms 3.0 will be released tomorrow, 21 Jul 2009. The first release of Simfatic Forms 3.0 beta was on 6th March 2009. The beta shaped a better Simfatic Forms. There still is a pretty long To-Do list; that will eventually be addressed in the upcoming versions. There are schools that are pro-beta and are [...]]]></description>
			<content:encoded><![CDATA[<p>Simfatic Forms 3.0 will be released tomorrow, 21 Jul 2009.</p>
<p>The first release of Simfatic Forms 3.0 beta was on 6th March 2009. The beta shaped a better Simfatic Forms. There still is a pretty long To-Do list; that will eventually be addressed in the upcoming versions.<br />
<span id="more-60"></span><br />
There are schools that are <a href='http://gmailblog.blogspot.com/2009/07/gmail-leaves-beta-launches-back-to-beta.html'>pro-beta</a> and are <a href='http://gettingreal.37signals.com/ch15_Better_Not_Beta.php'>against-beta</a>. There are several positive reasons to have a public beta and have the real users try hands on. I will keep that discussion aside for another post.</p>
<h3>Dear Beta participants, Thank you, Thank you and Thank you !</h3>
<p>I will send you the well-deserved license for Simfatic Forms Professional ASAP. Please allow one week; compiling the list and sending out the email is going to be a big task : ) ( Quickly scribble a Perl script? Where is my Perl reference book <img src='http://www.simfatic.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  )</p>
<h3>A humble invitation to Bloggers</h3>
<p>If your readers benefit having a quick, feature-rich form maker software, please do have a look at Simfatic Forms. See the <a href="http://www.simfatic.com/forms/faqs-pre-release.php">FAQ page</a> for details. The FAQ page contains a short video demo too. </p>
<p>Contact me ( prasanth (a-t) simfatic.com) with the link to your blog and I will send you a Free license. There is no obligation; your honest review is well appreciated.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/60/invitation-to-bloggers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
