Refactor: Implement Observer pattern

[hantoine]

After the lecture on MVC, I realized in MVC the controlleur is not the one asking the view to update itself.

In the future we will have to use the observer pattern, I suggest we fix our MVC by already using the observer pattern. The changes to make would actually not be that broad, just make RiskView implements observer interface and make the view call updateView on itself whenever it receives a notification from the RiskModel. This would require RiskView to have a reference to RiskModel that we thought was not something to do.

I could take care of this.

[hantoine]

I think the Gamecontroller Method might be better in a GameModel class, but this could be done after the build 1.

[hantoine]

Actually I'm not sure anymore lol. The teacher answered to my question that if the controller updates the view then it is not MVC, but on the slide 7 of MVC slides:
"the controller may also be responsible for updating the view"

[hantoine]

So I came to the teacher to ask a more precise question, he said that wether this can be considered as MVC or not is subject to debate, some people might say yes, others might say no. He also said he will not remove marks about that.

So in the end I dont think we need to make this for the build1, we could do it in the build2 since we will have to implement the observer pattern anyway.

[hantoine]

Done by hantoine. To be merged