If I dynamically decide and create what components go on the TWebForm and use TWebHtmlDiv to encompass them with dynamic html for the components, will that work? Or does the html describing the components have to be static?
I need forms that the client designs and then, their clients fill them in. I had a look at TMS Scripter, that doesn't seem to have that distinction. To the client's client, it should just look like a pdf being filled in.
I looked at several online form sites, they also lack this distinction or require the client's client to create an account.
Background Information
Just toying with the concept.
- I could get the Client to make a list of components to go on the form, saved as as a ini or json file.
- When they type in Name at design time, they get First_Name and Last_Name - labels and edit boxes, at run time.
- When they type in Contact they get Email and Mobile labels and edit boxes.
- Which means that the Html form is dynamic.
- The Form-Designer and the Form-Filler are separate applications.
- The Form-Filler is exposed to the public so it will be a separate url to the main application. I could write the Form-Filler in PHP, if required.
- When the client's client fills it and submits it, a pdf is generated and the information is saved into the database.