Hi Andy,
It occurs to me that Presenter class>>defaultModel is sometimes a very
useful thing in itself, and sometimes it's more a convenience for testing a
new presenter using the Show command in the CHB. The latter is true mostly
of expensive models that typically get replaced in real use.
The database front end (the thing that lead to all of the autogenerating
work) made the distinction quite clear. I've been adding #defaultModel
methods for testing and then getting rid of them for production because the
cost of making the models (only to be discarded) is noticeable (they require
database activity). For things like value presenters, the default models
are often of direct use, and I would _not_ change a thing.
So, I propose having the CHB Show command call something like
#showCommandModel that defaults to #defaultModel, allowing an override when
#defaultModel should be nil for performance reasons.
What do you think?
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
(352) 846-1287
Locked
