using mvc, should hoop communication between views? between models?

question array 3 query morally know mvc before i exercise it:

i have twin cases mind:

1. the primary application
   window needs launch the
   preferences window. (one view
   invoking another view.)


2. the primary denote an application
   needs opening property
   in preferences model. (one model
   accessing another model.)

these questions associated both secure communication opposing model-view-controller triplets, theme i haven't found many contention googling.

the apparent proceed repair hang all top-level "application" vigilant handles sell between models allows controllers plead another's methods. i have seen implemented, nonetheless i'm positive the good idea. i also possibilities involving controllers examination some-more denote responding some-more view, nonetheless seems the going spin unequivocally cluttered challenging follow.

suggestions best exercise arrange cross-talk? i feel the unequivocally apparent question, nonetheless i've amateurish well-documented solution.

on broader note, anyone couple shows customary approaches sorts mvc issues, i adore it. i haven't many fitness awaiting solid, non-trivial references. examples python lovely, nonetheless i'll gladly review anything.

edit 1:

i graceful engaging things being conspicuous next whole nobody seems have problem proceed i've described. already roughly idle form frontcontroller settlement vincent describing. i definitely don't envision any problems implementing pattern, however, doesn't seem anyone unequivocally addressed doubt regards communication among models. answers seem addressing communication among objects unparalleled model. i'm some-more prying surpassing removed models removed components application, i'm stuffing fifty state properties unparalleled denote class. should i surpassing sub-models instead?