Hey there all,
Wouldn't it also be good to take it another step and have the mediator use a model reference passed in with a notification so that the model is always what you think it is when accessing its properties? Just like view to view communication I was taught it was not a good practice and should be avoided if possible.
I just finished a project for Toyota/Scion that uses PureMVC and only had 3 weeks. Towards the last few days I had to do some "hot wiring" like this in order to not end up in a refactoring. In the end it worked and the code will never be looked at by others or extended. By hot wiring I mean mediator to mediator communication without using command/notification. I also had a case where I was talking to a model proxy through the facade instead of through a view notification reference.
I simply love how PureMVC helped me make it all happen in 3 weeks. I do not think I could have stayed on track and kept the spaghetti to a minimum without it. I am not a heavy 'patterns' guy but have adopted as much as I can to help keep my focus on functionality and design/interaction....instead of how my application will talk to itself.
I guess I am saying that stepping outside of your pattern usage is not too bad towards the end of a project that meets certain profile, but should be avoided as much as possible in the early stages.
Thank so much for this code base, it is truly a wondrous thing.
http://www.scion.com/rsxd/(btw I work for Solution Set in San Francisco and was the lead developer)