TonyM

> I would also have voted no to multi-line fields I tried to send a private message but have not worked that out. Here is an example of a great...

> A multi line edit area for text field and single line input for other fields. My point is do not do anything that stops such possibilities and others have...

@Jermolene I applaud the objectives of this piece of work and will do what I can to help, text and support this initiative. A couple of points about what I...

I am in the bush so cant review with a fine tooth comb. So friendly feed back. Do you actualy intend to drop the use of parameter:"value" and use "="...

I have returned from some time in the bush and a hot spot that had a broken usb connector so no Internet. I returned to review, thanks for your answers...

I just want to add the ability to include field content, or from a text reference, into "textural substitutions" is also important.

> > I just want to add the ability to include field content, or from a text reference, into "textural substitutions" is also important. > > For example: > >...

A passing depending on how you handle this would the use of text references be possible? All one needs to test is there is a leading !!, internal or trailing"!!"...

Jeremy, Regardless of the validity of the approach I suggested to permit fields to be included as references, inside these concatinations, is there a way to address this need "using...

> As it stands, the syntax for the examples you give would be `${ [{!!fieldname}] }$` and > `${ [all[current]get[fieldname]] }$`. This is sufficient and quite powerful as it stands...