MVC pattern - explained and applied

You teach as if there was only 1 type of MVC pattern. The one you teach here, is not the most common. Here the controller is just a Mediator. But, in the most common MVC pattern : Controller is responsible for handling View events (click, ...) OK, BUT also is responsible for registering the View as an Observer of the Model(which is indeed also an Observable), indeed the Model "only" knows Observers of itself. So this is not the controller that updates the View's (displayed) Business Data, but the View itself, as an Observer of the Model, that will be notified by the Model, via the View update method, in order to auto-update its IHM Data field(s). So in this case, the notion of Observer pattern is very important (as it isolates View from Model), and also the notion of Strategy pattern has to be pointed, while it is about choosing a specific Concrete Controller to handle the Views actions in a certain way, and also updates its look (but not its (displayed) business data). Also, there is a MVC version where the View knows its Controller, in order to send events to it. And finally, you missed a very important thing : MVC is based on Design Patterns, and you should have introduce Abstractions in here, Interfaces for example, in order that the classes that have to communicate can do it, just via certain authorized methods that are then the only thing that they know about each other ! When i began studying MVC i thought like you, that the MVC with Controller as Mediator was THE ONE. So, it would have been great to mention that the MVC pattern you teach here is not the only existing one, and the worst : you even said the contrary of that ! I nearly put 2 stars, but i want to encourage. May i would even say, that the pattern you teached is just a specific case of the Mediator Design Pattern.

Instructor presents the core concept (the MVC pattern) very well, and in straight forward way, along with a demo use case. It would have been nice to get a bit further in depth, for instance, by comparing and contrasting MVC with other development patterns. It would also be interesting to see an edge case where MVC would not be a good pattern choice, or perhaps, how to massage a different pattern into MVC and the advantages that could be gained this way. To restate, good intro.

Not what I expected, well, for $15, .... the whole red pen thing seems kind of unprofessional, well, I'm getting the point....I'll finish and let you know what I think.

I like the course. I am taking a Hybrid Mobile development course at UAB and this is part of the curriculum for the final project design. thank so much, John stokes hurrican7e@aol.com

Very good, succinct, well structured course with good pace, dictation and clear graphical presentation. Short, sweet and yet complete. Very much enjoyed the course and only wish the author had used C# instead of Java but admittedly that is a - nit.

The content in itself is useful, the videos just didn't reach my expectations. The videos didn't make me excited as I'm used to.

Covers the absolute basics pretty well. What it is missing is any consideration of business logic. Suppose you create a math application that adds 2 numbers. Where does the addition occur? I don't expect a lot of detail from a beginner-level course, but every real-world application contains something other than the presentation of the view and the handling of events. Where does it show up in the MVC structure?

Excellent explanation over the MVC structure. I will be using this in the java desktop application I develop. Simple and easy to understand excellent job.

Really enjoyed this course. Well explained and easy to follow. I recommend if you are new to the MVC pattern.

Well thought out course that gives you an insight into the MVC. Good example project shown from birth to working application. I recommend this course if you want to start programming using the MVC pattern.

Nice course! I'm starting to work with frameworks based on MVC, and this course is being really usefull. Thanks teacher !