What we need is not just a bigger dictionary of Oberon/F, although that might
be helpful: what we need is a thesaurus, and a copy of Bartlett's Quotations.
We need a document explaining, in detail, with clear examples, the large
number of messages sent and received by the framework. We need an expanded
repertoire of templates for the subsystem source code generator. A book
comparable to Hanspeter Moessenboeck's Object-Oriented Programming in
Oberon-2, but using Oberon/F, would be ideal.
Some few of the questions which I still have, which the proposal would not
help with at all, as far as I can see:
1) What, exactly, does Models.Bunch() do?
2) When should one use Views.ForwardCtrlMsg? when, if at all, should one call
a controller's or view's HandleCtrlMsg method?
Mayson G. Lancaster