MVC question

[Dipke]

Hi,

I have a model that extends Observable and a view that implements Observer.
With a Controller that checks the mouseclicks.

But when the user doubleclicks on the view another view has to be updated using the model.
So that means that the controller needs to extends Observable as well.
Is this common practice or is there another way.

thx

[JosAH]

So that means that the controller needs to extends Observable as well.

I don't understand your conclusion here: the Controler is notified by the View so it can create another view and registers itself as an Observer for that view again. I don't see where the controller as an Observable comes in ...

kind regards,

Jos

[Dipke]

The model is data from a file and the view is a table displaying the data.
When the user doubleclicks on a column from the table, the content from the column is displayed as a graph on another view.
It is the controller that receives the doubleclick so he has to notify the second view that somebody selected a column to display.
Thats why the controller (in my opinion) has to be an observer for the second view.

[JosAH]

The model is data from a file and the view is a table displaying the data.
When the user doubleclicks on a column from the table, the content from the column is displayed as a graph on another view.
It is the controller that receives the doubleclick so he has to notify the second view that somebody selected a column to display.
Thats why the controller (in my opinion) has to be an observer for the second view.

No, think of it this way: V ---> C <--- M where the View and the Model are the Observables and the Controller is an Observer (Listener most of the time). A Controller 'communicates' directly with Views and Models while the Views and Models simply 'signal' their changes to the Controller (through the Observable/Observer pattern or through the registered Listener mechanism). The Controller always is just an Observer.

kind regards,

Jos

[Dipke]

Hi Jos,

Ok that answers my question.
Many thanks.

Dipke

[JosAH]

Just FYI: my V ---> C <--- M model doesn't make the V and M talk to each other; the 'old' MVC model did allow it, but it is often considered 'cleaner' to make all 'communication' go through the middle C component. It makes the Controller more like a 'Mediator' (another design pattern).

kind regards,

Jos