a blanket of 10 user-admin-defined fields for each field type (ie, 10 text, 10 plain text, 10 combo, etc.). You could via a profile document turn off/on a field.
a field label system that would allow a user to say "the 5th user defined text field will have the label of 'email address'" etc.
All that, and obviously validation stuff etc is fairly simple to come up with... the problem is now field placement on a particular form...
if there was a WYSIWYG editor that would build the css on-the-fly and allow to you simply apply that CSS to the particular form, then you could (in theory) completely allow a standard end-user to create a form.
I dunno... the markup would be huge, but it's a way that it could be done.
And obviously there's other ways to do it - or should be others - but this is off the top of my head on a Saturday afternoon while watching the kids while my wife is out getting the Chinese food for dinner for us and our visiting family...
Stan,
I guess this could be done with the following:
a blanket of 10 user-admin-defined fields for each field type (ie, 10 text, 10 plain text, 10 combo, etc.). You could via a profile document turn off/on a field.
a field label system that would allow a user to say "the 5th user defined text field will have the label of 'email address'" etc.
All that, and obviously validation stuff etc is fairly simple to come up with... the problem is now field placement on a particular form...
if there was a WYSIWYG editor that would build the css on-the-fly and allow to you simply apply that CSS to the particular form, then you could (in theory) completely allow a standard end-user to create a form.
I dunno... the markup would be huge, but it's a way that it could be done.
And obviously there's other ways to do it - or should be others - but this is off the top of my head on a Saturday afternoon while watching the kids while my wife is out getting the Chinese food for dinner for us and our visiting family...
well, you get the idea!
-Chris