Comments on: Multiple Save Buttons http://creativebriefing.com/multiple-save-buttons/ for the marketer, designer, and entrepreneur Thu, 11 Mar 2010 06:50:47 -0600 http://wordpress.org/?v=2.8 hourly 1 By: HE http://creativebriefing.com/multiple-save-buttons/comment-page-1/#comment-4562 HE Mon, 05 Oct 2009 21:19:11 +0000 http://creativebriefing.com/?p=488#comment-4562 A solution I've used in the past is an invisible (1px x 1px) iframe. You then have the form submit to the iframe. On every form field you have a onchange=form.submit(). Basically, everytime a form field is changed it's saved. On the one hand this uses bandwith and database resources, on the other hand nothing is everlost yet the interface is seamless. This also allows for serverside form validation when needed. I do agree with short web forms though. I'm currently designing some online insurance applications, which are typically very long and complex. Instead, I've broken it down into sections for Insured Information, Risk Informaiton, Broker Information, etc. By using the above technique the user can flip through the different sections without ever losing data and having all the fields filled with database information. Hope that helps someone, A solution I’ve used in the past is an invisible (1px x 1px) iframe. You then have the form submit to the iframe. On every form field you have a onchange=form.submit(). Basically, everytime a form field is changed it’s saved. On the one hand this uses bandwith and database resources, on the other hand nothing is everlost yet the interface is seamless. This also allows for serverside form validation when needed.

I do agree with short web forms though. I’m currently designing some online insurance applications, which are typically very long and complex. Instead, I’ve broken it down into sections for Insured Information, Risk Informaiton, Broker Information, etc. By using the above technique the user can flip through the different sections without ever losing data and having all the fields filled with database information.

Hope that helps someone,

]]> By: SL http://creativebriefing.com/multiple-save-buttons/comment-page-1/#comment-4359 SL Wed, 08 Jul 2009 21:15:39 +0000 http://creativebriefing.com/?p=488#comment-4359 A solution I've used in the past is an invisible (1px x 1px) iframe. You then have the form submit to the iframe. On every form field you have a onchange=form.submit(). Basically, everytime a form field is changed it's saved. On the one hand this uses bandwith and database resources, on the other hand nothing is everlost yet the interface is seamless. This also allows for serverside form validation when needed. I do agree with short web forms though. I'm currently designing some online insurance applications, which are typically very long and complex. Instead, I've broken it down into sections for Insured Information, Risk Informaiton, Broker Information, etc. By using the above technique the user can flip through the different sections without ever losing data and having all the fields filled with database information. Hope that helps someone, A solution I’ve used in the past is an invisible (1px x 1px) iframe. You then have the form submit to the iframe. On every form field you have a onchange=form.submit(). Basically, everytime a form field is changed it’s saved. On the one hand this uses bandwith and database resources, on the other hand nothing is everlost yet the interface is seamless. This also allows for serverside form validation when needed.

I do agree with short web forms though. I’m currently designing some online insurance applications, which are typically very long and complex. Instead, I’ve broken it down into sections for Insured Information, Risk Informaiton, Broker Information, etc. By using the above technique the user can flip through the different sections without ever losing data and having all the fields filled with database information.

Hope that helps someone,

]]>