Thanks for the reply.
1st - Regarding my code below - I was considering passing the FormType (radio, text, textarea) variable througha if / case or tag that appropriate spits out the same code.
Your right -they all essentially do the same thing.
As for terra forms - I have watched that product page and watched the samples grow and grow. I have considered many times - but all too frequently by these code pieces or tags and find they are not easy to use, limited etc. I do however plan on downloading terraform and giving it a try.
Personally since I purchased your tag sortable about a month ago- and was pretty happy with the code I will give terra forms.
I had seen that demo on the dynamic form generated -but not sure how that all works into your tag so am curious. It seems as if you have already done what I am looking to do here.
And I liked terra forms file upload enhancement. ( I am faced with quite an elaborate file upload / tag / note it type solution )
Anyhow - The basis for all this was that I am tossed between html forms and flash forms and then thought - hey - if I store the information about the forms in a database - can I use it not only for html forms, but to create an XML document to help develop flash forms - then further more - PDF forms etc....
Thanks for the reply!
Jason
P.S. - I added a few lines of code to your sortable to support images - makes it even more fun to use!
>It's certainly possible, and I've seen it done a few times and done it
>myself many times. The biggest problem is that HTML form fields have such an
>inconsistent interface. For example, compare the HTML markup for a set of
>radio buttons with a select box: very different, yet the two widgets
>effectively do the same thing. I use a product called TerraForm [disclosure:
>I sell it] to build forms which acts as an intermediary between the
>developer and the HTML, providing a consistent markup. This makes doing what
>you want to do much easier as the appearance of the field is simply
>controlled by one database field. Example here:
>http://www.eswsoftware.com/products/terraform/gallery/dynamic.cfm . Also,
>check out this product by Bill Kaigler:
>http://www.cfcodewriter.com/content.cfm?contentnbr=41
>
>
>
>With the code you have written below, would you have one record for each
>radio button? How about one record for all the radio buttons, then another
>field containing a list of allowed values. You could use the same syntax for
>checkboxes or select boxes. I'd also recommend a field for a human-friendly
>field name, and a field tracking whether the field is required or not.
>
>
>
>
>
> _____
>
>From: [EMAIL PROTECTED] [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, 28 July 2004 1:24 p.m.
>To: CF-Talk
>Subject: Help! - Dynamically Generate Forms from SQL DB - Bad Idea?
>
>
>
>Hello List -
>
>I am looking to store information about variables nad form fields in a db to
>conditionally build html forms -
>
>
>Has anyone stored the variable name, and the form type in a database - and
>built the form dynamically on the fly?
>
>I can't seem to find any references to it and am thinking because it must be
>a bad idea.
>
>Basically - store
>name | type | state
>LastName text
>LastName text
>HowToContact radio checked
>
>Then build components that write the html form- ie - if it's a radio button
>-
><cfoutput><input type="#type#" name="#VarName#" #state#></cfoutput>
>
>Another purpose is - if I decide to do forms in Flash - perhaps I can have
>the database spit out an XML document to use to build the flash interface.
>
>Perhaps have the DB spit out XML/ or another format to build PDF forms
>etc....
>
>Too complex? Bad Idea - Any products already allowing this (NOT Hosted
>servies)
>
>Thanks!
>Jason
>
> _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
