From: Friedrich Dominicus <frido@...>
Date: 2002-09-17T21:33:28+09:00
Subject: Re: MVC and OO Design?

ddet@gmx.de (Det) writes:

> Friedrich Dominicus <frido@q-software-solutions.com> wrote in message news:<87hegq5wes.fsf@fbigm.here>...
> > This is correct the Modell notifies the Controller or the other way
> > round the Controller queries the modell for needed input 
> 
> Hum, there are some different views of what a controller
> is or how the M, V and C should look like. They are much
> influenced by the GUI-framework one uses or the overall
> architecture which should be built.
> Therefore MVC is in modern reading not named a 'pattern'
> any more but a 'paradigm' (and everytime causes a lot of
> discussion in developer teams).
Thanks for the clarification. I probably did understand it
differently. 
> 
> As with the classical view IMHO there is a triangle 
> between M,V and C. So the Modell notifies the *View*, not
> the Controller.
Well I posted an example, why don't you do the same as how you see it?
It would be helpful for discussion. I don't think that I agree with it
because with that I do get a sort of coupling between the View and the
Model. 
> The Controller does not query the Model per Design.
> (This is only a hidden technical aspect, if necessary to
> do his job).
Well for me that is the point. The controller sit's in the middle,
waiting for things to come. If the Model changes it request the View
to update to the new standard. But the Model doesn't knwo anything
from the view.... 

> 
> > forwards it
> > to the Model get back the values from the Model and than 
> > updates the View. 
> 
> The Controller does not update the View in the above
> mentioned scenario. The View (displaying part of a GUI)
> updates itself (ok, based on push or pull ...).
> The Controller updates the Model caused by events 
> coming from the GUI-Controls (User).
Well could you show what you mean in code?

Regards
Friedrich