instantiating views and controllers

[el_chief]

i have a form that i'd like to instantiate at runtime, as well as its controller

is it better to do a), b), or c)?

a) instantiate the view, and then the controller (or vice versa)

b) instantiate the controller, which then instantiates the view itself

c) instantiate all the controllers at startup, and only worry about instantiating the views as needed

what are the advantages or disadvantages to each?

thanks!

[mitchellsimoens]

Views should be "dumb" and the app controlling done in the Controller. So instantiating the Controllers should be done first.

[el_chief]

Sounds like the recommend approach then is more model-view-presenter with a passive view, or perhaps supervising controller, yes?

[mitchellsimoens]

There are lots of different MVC ideals out there so it's kind of up to you to decide what's best for the application. The strictest is that a View should not know about anything outside of itself, an example is that it shouldn't even know what children is should have. The Controller should tell the View what children to have.