MVC v MVVM where to store view data

[Timmy Ryan]

In a swing application where there are multiple views some of which can affect the layout of other views what is the best way to handle the flow of information?
To store the view data in a corresponding model such as in MVVM, where the controller updates the model and the model then through the observer pattern informs the observing views to update themselves. This is the presentaion pattern I believe.
I understand to have one view update another is not a good idea.
Are there any other ways that are practical?