iKilledMyFunny Data binding is more of a web centric term that is very similar to how we refer to the controller here. When something is changed in the interface that change is funneled to the model and vice versa

Hi @NC699! I definitely read comments and appreciate your query. Data binding is a great concept and does indeed play a role in MVC, albeit less traditional. In a conventional MVC, you'd manually update the view via the controller after model updates. However, with data binding, the view can update automatically when the model changes, which leads to reducing the responsibilities of the controller. But the controller is generally still needed to handle user interactions and often inputs into the model. You would go about this by linking your model's variables to your view. The mechanism and code specifics would depend on the language and framework you're using. Don't hesitate to ask if you want a tutorial on implementing this!

Your welcome :) MVC allows you to separate the interface that the user sees from all of the code in the background. That way you can change the code or the interface on their own without effecting each other. It adds flexibility most of all and keeps changes from ballooning into multiple errors

Hi @stacktrace6227! Great question and thanks for watching the video! The main point behind using MVC (Model-View-Controller) in your applications is to separate the concerns of your code. The model will handle the data and calculations, the view is responsible for your interface, and the controller coordinates interactions between the two. This separation usually makes the code cleaner, easier to manage, and increases flexibility. Plus, it can help with team projects, as different people can work on separate parts simultaneously without stepping on each other's toes. It also makes debugging easier, because if an error arises, it is generally clear which part of the code (model, view, or controller) it came from. Hopefully, this clears things up for you - happy coding!

+K Badsha I do use some strange techniques. I'm glad they worked even though they might not have been that enjoyable.

Hey @qaipak1, I understand that different teaching styles can appeal differently to each individual. As long as you're finding it effective and you're learning, that's all that matters! I appreciate your candidness and thank you for sticking with me. If there's any way you think I could improve or specific things you'd like to learn, never hesitate to let me know. Happy coding!

tommy988lo It does keep the view and the model separate, but not in the normal way that we would use the term encapsulation which is normally based on protecting object data

Hey @tommy988lo, good question! The Model-View-Controller (MVC) pattern does indeed use encapsulation. It is one of its primary strengths. In this tutorial, encapsulation is depicted where we separate our program into Model, View, and Controller. The 'Model' encapsulates all the data and calculations, it doesn't know about the existence of the 'View'. The 'View' encapsulates the interface part, it doesn't know about the calculations happening in the 'Model', it only displays the resultant data. The 'Controller' acts as an intermediary, it encapsulates the interactions between the 'Model' and 'View'. It's taking care of updating the 'View' based on the data changes in 'Model', and altering the 'Model' based on user input through 'View', without revealing how this is done internally. You can consider encapsulation as the MVC’s mechanism of keeping the integrity of data by keeping it private and accessible only through methods. It separates the concerns and reduces the complexity. Thanks for the great question!

***** Thank you very much :) Yes I have been working to make the code much more readable. Since I write this out of my head a lot I get sloppy with my naming. Sorry about that.

Hey @kenmtb! I'm glad you found the tutorial helpful, your kind words are very motivating. Taking your feedback into account, I'll make sure to use more descriptive java control names in my future tutorials to make it even simpler for everyone to understand. Your feedback is valuable to me, it helps me improve the content. Keep watching and happy coding!

thekill129 In some situations just defining a model, view and controller is considered an MVC. The only problem with doing that while not separating the model from the view is that you lose the flexibility you gain through the MVC pattern. I demonstrate a true flexible MVC in this situation.

Hey @thekill129! Thanks for reaching out. I definitely understand your confusion - MVC architecture can be tricky! The way it is implemented can vary slightly across frameworks and programming languages. In my tutorial, I presented a simplified and straightforward implementation of MVC in Java which is primarily for learning purposes.

Indeed, in some variant implementations of MVC, the View does have knowledge of the Model, and the Model doesn't have a direct awareness of the Controller. But in a true MVC pattern like the one I showed, the Model is solely responsible for handling data and its manipulations. The View presents the user interface and handles user interactions. The Controller acts as an intermediary that controls the data flow between the View and the Model.

The key takeaway here is how it helps in separating concerns and maintaining modularity, regardless of whether or not directly aligning with the formal definition of MVC. Always remember, the primary goal of MVC is to separate the representation of information from the user's interaction with it. The specifics can sometimes vary depending on the design and needs of the application.

Hope this clears things up a bit! If you've got any more questions, don't hesitate to ask. Happy coding!

The answer is that you can create them in both ways. I always try to keep the view and models completely separated when ever possible. Design patterns are just guides for how to make your code more flexible and aren't definite rules like many people teach. That is just my opinion though :)

Hi @toucanlam! Thanks for your really thoughtful comment! 😊

You're right in observing that there are a variety of ways to implement MVC, and some do indeed create a more direct connection between the view and model, allowing the view to observe the model for changes.

In the context of my tutorial, I was aiming to simplify the MVC pattern primarily to facilitate learning for those new to the concept. This is why I chose the model, view, and controller to have their own distinct roles and not 'know' about each other.

However, the beauty of MVC lies in its flexibility, and it can be adapted to the complexity and requirements of the project at hand. For a larger application with multiple views reflecting the same data, you're absolutely correct that having the views observe the model can be beneficial. Such an approach can lead to a more dynamic and responsive user interface.

Remember, the main goal of MVC is to separate concerns, making the code easier to maintain and understand. The exact implementation may vary, but as long as you’re maintaining that separation of concerns, you're on the right track!

Feel free to continue asking questions and engaging in this great dialogue! Keep experimenting and learning! 😊👍🏼

You're very welcome :) I don't do tutorials for anyone except YouTube and I don't sell anything.

Hi @Claymore2408! You're absolutely right. Understanding the MVC framework is indeed essential before diving into other frameworks like Spring or Grails/Groovy. As for your question, no I don't work with Guru99. However, it's interesting to know there's someone out there who shares a similar accent and voice with me. Maybe we were separated at birth, who knows 😂. Anyway, stay tuned for more Java tutorials. And, as always, feel free to ask anything if you're stuck somewhere. Until next time!

+Clark Mask Ummmm, I'm sorry about the Lumbergh voice mmmmk ... Ummm, I'm gonna need you to go ahead and watch this video again tomorrow. So if you could watch it around 9 that would be great, mmmk ... And, I almost forgot ahh, I'm also gonna need you to go ahead and watch it the next day too, kay. :)

Hey there @theclark984, glad you liked the tutorial! Uh...yeah... I'm gonna need you to go ahead and take that as a compliment...because I am. So, let's just go ahead and learn some more Java, mmmkay? Hahaha. Keep enjoying the vids, and if you have any questions, don't hesitate to comment!

You are so right about that. It used to drive me insane when people used jargon during lectures and I go out of my way to make everything very understandable. I'm happy I was able to clear up MVC :)

Thank you @spooky_zen! Being able to simplify complex topics is part of the joy in teaching. I'm glad you found the video helpful and easy to follow. Always aim to cut through any unnecessary complexity, because at the heart of it, coding is about solving problems in the simplest way possible. Appreciate you watching and engaging!