This technique has little verbosity beyond the actual code to generate HTML, and works great in a Design Template-context. It supports modularity, as each field is a potential module. Since the templates are forms, the dynamic "modules" also work in stored documents.
You can combine Java (through LS2J), formula (through Evaluate) and LS , just like you can when you're using agents for templating web-pages. If you're a Java-guy, then you probably would need a little more code (testing field names with Regular Expression) to achieve the same.
Combine this technique with @UrlQueryString in Form Formula if you want the ability to present data in several content-types.
The technique relies on Execute, a WQO-agent and field-names following a pattern. I chose Execute because it's faster than making a testing-routine for patterns. If you're planning on putting this technique to use in real applications, I suggest you use Regular Expressions, Instr, etc. to look for valid field-names, as Execute is horrible to debug.
I have one pattern that I look for in a field-name, "wqo_actonfield_". The third token (separator = "_") is the method to be executed. The rest of the tokens are ignored to allow several fields executing the same function.
You could also have the rest of the tokens being parameters for the method being executed.
For instance field named "wqo_search_google_dontpanic" -> run a function that inserts HTML with search-results into the field.
>> Demo Application.
WQO-agent for demo:
Form, one demoBody-field:
Form, six demoBody-fields:
Result, web (click for full size)
As always, comments are appreciated :)