The form builder would use a desciption lanugage like the current one used for categories. It would allow you to specify plugin scripts that wouod be used for processing that form. For example you may want to have a user poll about a subject. You would create the form set it to use the polling plugin, it would create the data storge mechnism needed and the reporting views for that poll.

-- HaroldGottschalk - 31 Jul 2000

I like the idea of extending the TWikiCategoryTable to be used in a more generic way. Maybe something like %FORM{"name" script="dosurvey" template="dosurvey"}% would show an HTML form defined by the dosurvey.tmpl template, which has a category definition as described in TWikiCategoryTable. Submitting the form would call the dosurvey script which does some action based on the form data like creating new topics. Some default do* scripts could be created, like for example dosurvey , dovacationrequest or doexpensereport . Well, extending that could lead to a full blown WorkFlowSystem built on top of TWiki.

In fact, the TWikiRegistration is already somewhat generic but in a different way. You can add any number of items (i.e. a phone number) to the form by simply editing the registration topic. The register script is intelligent enough to figure out the items and creates a user topic with an unsorted list out the form items.

-- PeterThoeny - 31 Jul 2000

I like the idea of using %FORM{"name" script="dosurvey" template="dosurvey"}% for forms. 2 things though, one is that if the script and template have the same name you should be able to just say %FORM{"name" script="dosurvey"}% with the default template name set to be the script name. The other thing is that sometimes you may want to use a form on a remote server so you should be able to use a URL instead, eg. %FORM{"name" script="http://search.yahoo.com/bin/search" template="search_yahoo"}% .

-- JamalWills - 01 Aug 2000