On 5/5/06, Andy Matthews <[EMAIL PROTECTED]> wrote: > > What I'm talking about it is to create a generic form processor. You feed > it > some values and it does all the work for you. The goal being that you'd > never have to manually type out any of those values any more (except in > the > form setup). You just create your form as normal, point the action > attribute > to this form handler and that's it.
The idea is to cut down on the work as much as possible. What you are proposing could just as easily generate the display for the form itself (prior to mailing). Take it a step further, and it could handle the edit display for the form as well. Instead of using params you pass to the processor, you could store the params in a DB (field name, field label, required, field type, maxlength, database field type, etc..), and you'd have yourself a content management system. My attempt at this has been interesting. I went the route of not even using standard table structure, and instead opted for single "data type" tables. One for varchar, one for text, one for longtext, etc.. While that did render a sort of flexibility, I'm taking a hit on the database end, because MySQL isn't really designed around that idea. You end up with tons of joins, obviously, or temp tables. I had to start using "cache" tables. I'd already had a "quiz/survey builder" that only stored the datatype and then created/modified a table to store the data, which is basically where I'm back to. Perhaps with a different DB it would make sense to use the single table per datatype idea. These object databases are starting to pique my interest... :DEN ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:239725 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
