My model in my MVC pattern, generates components at runtime and gives them to the View to be displayed on the screen through update() method (you know, model is the observable and the view is the observer). But I also need to add listeners to these components, and the controller has the listener methods (because they say the MVC pattern is like this) and it’s not involved in this update process. So I can’t add the listeners at runtime, but only in the controller’s constructor at startup.
I’ve got an idea, that is making the controller the observer and then giving the data to the view, as well as adding the listeners. Do you think this would be OK?
Yup, making the controller your model observer to allow it to update the view would definitively fit, to my mind, in MVC orthodoxy.