I have to admit that I'm kind of a - dare I say - diva - when it comes to forms. I prefer to type them out and do all the validation by hand. In the past I've written form 'helpers' to handle generating and validating forms (*), but I haven't done that for quite some time. I feel like I've written a few million forms in my life time, and I'm sure I'll write a few million more.
This week a coworker introduced me to WuFoo. WuFoo is an online form service. As you can guess, it lets you build forms and host them on their server. It handles storing and processing all the results.
What is truly slick is how they handle all the editing. Everything is drag drop, so to add a form field you simply drag over the type of form field you need. You can then double click on the field to edit the label, set requirement status, etc.
It has a slick reporting UI as well. I can build a form with a radio button and design a form that uses a pie chart to display the results.
When would I use this? Probably never as I know I can whip out a quick form in a few seconds. But for folks who don't have access to Me (I'm not cheap ;) or may not even have a web site, this is sweet service.
Feel free to play with the form I created.
Archived Comments
Now you almost got me. I was reading your statmemnt and go to "When would I use this? Probably never as I know I can whip out a quick ..." when I eyes got real wide because I just knew the next words were going to be "... CFC to let me do this in ColdFusion."
I've been using the Uniform Custom Tag library by Matt Quackenbush to easily create consistent, accessible forms that are easily skinned.
Have a look: http://www.quackfuzed.com/i...
I haven't used it, but you could checkout cf_sebForm (http://www.bryantwebconsult....
"The cf_sebForm custom tag simplifies development of simple forms. It separates logic and display, integrates with CFCs, and manages validation. The output is unobtrusive and skinnable."
As an aside, note I used * in the blog entry. I had meant to add the following as a PS.
Back in my Perl days, I built a few standard libraries. I used a common naming scheme that I brought into my early CF days.
Every app was named somethingGod.
So my form code was FormGod.
SIlly - I dn't know what I Was thinking.
"I have to admin that I'm kind of"
shouldn't it be "I have to admit that I'm kind of"? :)
Can I pretend I meant that?
Even if you don't use WuFoo for actually constructing a form, I love it for helping with the skinning of forms. There are a bunch of pretty cool themes to choose from, and it's nice to see something like an end result of color combinations before actually diving into coding it.
This one is pretty good too, in PHP: http://www.phpform.org/
There's also a CF one believe it or not, 'cause I wrote it a while back but not launched to public. :)
The discussion is an interesting one, however we kind of think that a form needs to do more than just display and report on data with a chart. Our approach is that the data is the most important reason for creating a form in the first place so to make that a reality you need a decent backend to effectively do more with the data. We think you should be able to create a form to elicit data and then make that data available to other processes as needed. Sometimes it might be a simple spreadsheet but other time sit might be a more usbale applciation, like CRM, ERP, Accounting, etc. We've built putoo in XML using the eXisat d/b XML engine and we can expose the collected data via Web Services to any other app that wants to grab the data. It's all too hard if you have to do the initial collection and then do it again if you want to reuse it in some otehr sorporate app.