I've got this project which is kind of One Form To Rule Them All.
We have all kinds of forms around the corporation which people are obliged to use for all kinds of things, get access, change access, request new directory and so on.
The people who deal with these forms don't know HTML/CGI at all and I'm constantly being asked to add someone to the distribution list, add a field, make a field compulsory, rename or delete etc.
So I thought the sensible thing to do was create an interface to manage and edit other forms. That way I can just have "form.cgi?id=1" and "form.cgi?id=2", and maintain them via "editform.cgi?id=1" and "editform.cgi?id=2" rather than fifty different html documents all needing to be kept up to date.
I'm assuming I'll do this via DBI and SQL, but what do monks think the setup should be?
What I'll need is to maintain an arbitrary number of forms, each with arbitrary numbers of fields of any form type (except upload), with arbitrary text to go both before and after them; fields need to be flagged as required or optional; the fields which are of type radio and select and checkbox will of course need to hold arrays which can be added to or deleted from.
I suppose users might also want to change the order of fields from time to time as well as insert a new field between existing fields. That's something I haven't coded before, a "move this item up one", "move to bottom", "move to top" etc. kind of thing.
Any initial thoughts to get me started would be appreciated.
--
Every bit of code is either naturally related to the problem at hand, or else it's an accidental side effect of the fact that you happened to solve the problem using a digital computer.
M-J D
In reply to Meta-form: database setup suggestions please by Cody Pendant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |