Well, you can. But you'll be lucky to find a tutorial for every single combination of design patterns possible. The point is, you understand how both work individually, and if you see a need for both (and Observer often plays a part in MVC anyway) you can design it yourself. To be honest, if you're looking for a tutorial on how to do this, I'd guess you are trying to re-shape your problem to fit a pattern, rather than apply a pattern to your problem. Wrong way round
Hi!
Sorry for the delay, I have been away!
I hear what you are saying. Can you then recommend me some Observer guide?
Can you please give me some tips on how I should design the program.
This is the design problem I have:
In the program there are about 4 different components where each component is well suited for the MVC-pattern.
These for components depend on each other. So for example if the components are A, B, C and D, D can depend on A, B and C. But B only depends on A and B. "depend" may be blurry. In the first case were D depended on A, B and C. That means that when something happens in A, B or C. They will have to update/call a method or something like that in D.