Forms need to be as easy to create and maintain as possible. It should be possible for them to maintained by non-technical persons.
The approach under consideration is inspired by Adrian Smith's galleries and illustrated with Eric Lescasse's function ConferenceDemo5. This function puts up a somewhat complicated and certainly attractive Windows form using his Objects. Adrian's "gallery" approach suggests we can separately store reference data saying that when this "field name" (or "control name") is used, we'll handle it in such and such a way.
It seems that we can write a general facility which will have the following properties. (To allow searching in a workspace, a "q" is placed in front of each of these properties.)
Specifications for the form can be unique to the form as in delta-SS in FORM.w3 (except that delta-SS has fixed columns which must be variable).
Or, specifications can be obtained from (READS 8100 58). Same property specs are shown below. A field named "drug" has valuetype "text". A field called "dose" is right aligned. A field called "sex" has two options, "female" and "male" and female is checked.
Thus it should be possible to create a Windows form with the following syntax.
MakeForm 'Name' 'Fname' 'OKButton' 'CancelButton' 'APL' 'Sport' 'Smoking' 'URL' 'Age' 'WebBrowser'
And it should be possible to create an HTML form with exactly the same syntax, or perhaps with a left argument to MakeForm. (MakeForm is presently implemented with the name "qkeFN". GugScript & qkForm are a highly developed implementation).
Other characteristics of this process include....