MVC, nesting view, nesting model?
Hello folks,
I'm trying to figure out how to wire the models and views I have.
I have three models that represent three separate applications, that are combined into one shell application. Each model has its own view(s). Easy enough.
One view has yet another micro-application nested within itself. Let's say via the mainmenu in this view you can open a mini application that only belongs to said view. This is so, because once the mini application is done, that view updates itself (they both tap into the same database). The nested mini application is self reliant and has its own model, because it could be a stand-alone application as well.
Ok, so here is what I'm wondering about: how does the view containing the mini application make the mini application show up? It should probably relay an action from the mainmenu to the controller, which decides what to do with it. Should the mini app's model be nested within the other model? That seems odd to me, since they don't directly relate to each other. The mini app should be displayed as modal, so the view with the menubar should somehow know it should be disabled (through a model update, or more likely directly by the controller). So will the controller create the miniapp model and wire a view to it, while disabling the view with the menubar, all with method local variables? Is the main model at all involved or kept in the loop somehow (it seems to me it should be left completely alone)?
The problem is ofcourse that the mini app appears to be a dialog that belongs to the view that made it pop up. Yet there's some relation between those completely separate applications in that the instigating application should be put on hold for the mini application.
Some help please?
