Your videos are so good. I wish you were my design patterns prof. Your 6 to 10 minute videos are waaaaaaay more valuable than my professor's hour of lecture 🙂
This login example is hard to understand. I watched it two times, still didn't get it. Why a login button should be generic? A button for say Register can be different from a button for login and both classes can extend a button interface and do independent job. You can implement airplane example.
Great video but I'm finding quite complicated to understand something on the example used in 3:18, the LoginButton constructor method, should also set the mediator? meaning that the Dialog class should instantiate a the LoginButton using itself as parameter?
@@geekific I understood with a different video from you, this one is missing the main method, where you usually set the mediator. Thank you for all this teaching!
The code in this one doesn't feel quite right. The whole point of mediator is to encapsulate communication between colleagues . The example used here though not technically incorrect, didn't capture that clearly for learners, since only one colleague(LoginButton) is calling the mediator. I had to watch another video to get it.
Hey man :) An interface in Java just defines the behaviors a class must implement, it says what an object should do but not how it should do it! I suggest you take a look at the OOP Fundamentals video: th-cam.com/video/Vfk6sExu8-4/w-d-xo.html and Design Patterns Introductory video: th-cam.com/video/mE3qTp1TEbg/w-d-xo.html before diving in the actual pattern videos. After these, you can start by watching the Creational Patterns Series, as they are usually "easier" to grasp if you are getting started with design patterns. If you need anything else let me know! Cheers!
Your videos are so good. I wish you were my design patterns prof. Your 6 to 10 minute videos are waaaaaaay more valuable than my professor's hour of lecture 🙂
Glad to be of help! Thanks a lot for the support
You should have shown the UML class diagram of your example
This login example is hard to understand. I watched it two times, still didn't get it.
Why a login button should be generic?
A button for say Register can be different from a button for login
and both classes can extend a button interface and do independent job.
You can implement airplane example.
Hello, thanks for the feedback and sorry to read that! Will keep this in mid for future videos :)
Great video but I'm finding quite complicated to understand something on the example used in 3:18, the LoginButton constructor method, should also set the mediator? meaning that the Dialog class should instantiate a the LoginButton using itself as parameter?
The mediator is set with the help of the setter method. I am not sure I got your question!
@@geekific I understood with a different video from you, this one is missing the main method, where you usually set the mediator. Thank you for all this teaching!
Your video's are just amazing !!! but for this one I find it so difficult to understand. :(
Please let me know which parts were confusing for you so I can help! Cheers :)
The code in this one doesn't feel quite right. The whole point of mediator is to encapsulate communication between colleagues . The example used here though not technically incorrect, didn't capture that clearly for learners, since only one colleague(LoginButton) is calling the mediator. I had to watch another video to get it.
Thanks for the feedback! Will keep it mind for upcoming videos :)
What should I google to find the other video?
Since all design patterns involves interfaces. I find personally difficult to grasp it. May be I should read again and again.
Hey man :) An interface in Java just defines the behaviors a class must implement, it says what an object should do but not how it should do it! I suggest you take a look at the OOP Fundamentals video: th-cam.com/video/Vfk6sExu8-4/w-d-xo.html and Design Patterns Introductory video: th-cam.com/video/mE3qTp1TEbg/w-d-xo.html before diving in the actual pattern videos. After these, you can start by watching the Creational Patterns Series, as they are usually "easier" to grasp if you are getting started with design patterns. If you need anything else let me know! Cheers!
Very difficult to understand please use some highlighting arrows when you’re explaining each part of code
Thanks for the feedback! Will try to do my best!