Re: Extending a third party tagged type while adding finalization

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 04/12/2017 15:59, Robert Eachus wrote:
> On Monday, December 4, 2017 at 2:58:25 AM UTC-5, Dmitry A. Kazakov wrote:
> 
>> You mean MVC using all static object? I don't think that is possible
>> with or without tools.
> 
> No, I mean/meant to have it possible to write the model, view, and
> controller separately, then have a tool combine the three aspects.
Why a tool? What's wrong with connecting/attaching instances?

> So the controller could be used to do multiple changes, then a call
> to run causes an initial call to display.

Usual technique is to freeze view notification when doing bulk updates 
to the model. The easiest way is to detach all views, do updates and 
attach them back. This is how GTK deals with MVC.

> The controller will also make calls to display, as will the model
> from time to time (modeled time in a simulation, or test harness).

MVC is a synchronous model which pushes updates. If you aim at real-time 
systems you would rather use a view that pulls periodically regardless 
of any updates. That is not classical MVC.

> The goal is not only to make it easier for the programmer to think
> about the different aspects while programming them, but to minimize the
> scaffolding that the programmer must write. Done well, the view mode
> would use default values for display objects and it would be possible
> for the programmer/user to move things around, resize them, change fonts
> and colors, and save all this in a config file.

Most frameworks separate all that from whatever model. These things 
handled as properties/styles of the widgets of which the view is 
constructed. Throwing all into one heap won't make things easier, IMO.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de