Phil is very precise with words even on a casual statement. Robert has a tough time . Haha I've seen Phil correct Roberts statements at least a dozen times. but this is just friendly corrections. :). Best videos in the internet for Design patterns. 👍😎
In the example with espresso, it seems that we duplicate the Ingredients list each time we add a decorator (each decorator maintains its own list of ingredients which contains all previous strings plus a new one). Why we can't add to BaseCoffee class the List private field and public methods that allow us to add elements in and retrieve information from this list. In this manner it could be similar to the event system. In general, if I suppose that my object can be modified then I add the property which stores the list of applied modifiers and some method that iterates over this list to define a final state of the object.
Hello! I've got one question. In the EspressoShotDecorator we stack up all the decorated coffe ingredients plus the espresso. But for the cost we just add .55 to our cost, without considering the decorated coffee cost. This way, the espresso shot is gonna cost 0+.55 I think.... Or am i missing anything? Nice Tutorial by the way! Cheers! Antonio
4 years late but whatever. The first instance of the coffee "BaseCoffee" has a price of 1.50, and when you decorate it with the espresso you add .55 to that, totaling 2.05. As far as I know you will always need an instance if ICoffee in order to create a espresso, so you can't just instanciate an espresso by itself.
Very very nice design patterns series ... Very nice real life examples and explanation by Philip .. thanks for posting such informative vedio .. plz post more designs patterns vedio
nice info guy's but maybe next time get a maybe a diagram , or even some uml schematic .. just the code allone makes it hard to follow Judith Bishop did a nice book on the subject years ago "C# 3.0 Design Patterns" published by O'Reilly
Hard disagree. Everybody else puts up Visio slides labelled A and B, while these two have a CONVERSATION and talk with their hands. It's brilliant, and easy to follow, for me at least.
I couldn't find the link to the design pattern playlist, could someone please link? Thank you! Edit: Found it th-cam.com/play/PLT2NrqLzZng3YMek58eVZVkBiW3NyVSef.html
JS has no types. It means, decorator pattern doesn't apply because all the abstraction for flexible design is available without interfaces or abstract base. That being said, how would author claim that if he knew decorator pattern, it would save lots of time etc in his JS project. This is nonsense
Console Visualizing Data Transmission Portorate Bypass Polar Design Pattern if 0 else 0 function 0/00 Point Position Power 0^0/00 Omega Clock Signature ‰ Com Theta.
Full list for this series:
0. SOLID Design Patterns (start from here): th-cam.com/video/agkWYPUcLpg/w-d-xo.html
1. Design Patterns: Command/Memento: th-cam.com/video/zRbHlDeon3E/w-d-xo.html
2. Design Patterns: Strategy: th-cam.com/video/QZIvlny1Onk/w-d-xo.html
3. Design Patterns: Template Method: th-cam.com/video/MfAvs0n9uMs/w-d-xo.html
4. Design Patterns: Observer and Publish-Subscribe: th-cam.com/video/72bdaDl4KLM/w-d-xo.html
5. Design Patterns: Singleton: th-cam.com/video/sbML3xFHRbI/w-d-xo.html
6. Design Patterns: Factories: th-cam.com/video/JEk7B_GUErc/w-d-xo.html
7. Design Patterns: Adapter and Façade: th-cam.com/video/XYa0rmRMZ1Q/w-d-xo.html
8. Design Patterns: Decorator: th-cam.com/video/6PPMR0GWrZQ/w-d-xo.html
The cost for the ExpressoShotDecorator should be Cost = decorator.Cost + .55M;
Phil is very precise with words even on a casual statement. Robert has a tough time . Haha I've seen Phil correct Roberts statements at least a dozen times. but this is just friendly corrections. :). Best videos in the internet for Design patterns. 👍😎
Yeh total clash but it works
Clear and excellent explanation. Thanks!
Hi, nice explanation, thanks for sharing this. In the next videos it would be great to also have an example how the client would use this.
Why almost all of the videos about decorator pattern talks about coffe shop..of course bcos the book uses coffe shop as the example
Thank you for the simple explanation on the decorator pattern :) that was very helpful
In the example with espresso, it seems that we duplicate the Ingredients list each time we add a decorator (each decorator maintains its own list of ingredients which contains all previous strings plus a new one). Why we can't add to BaseCoffee class the List private field and public methods that allow us to add elements in and retrieve information from this list. In this manner it could be similar to the event system.
In general, if I suppose that my object can be modified then I add the property which stores the list of applied modifiers and some method that iterates over this list to define a final state of the object.
Hello!
I've got one question. In the EspressoShotDecorator we stack up all the decorated coffe ingredients plus the espresso. But for the cost we just add .55 to our cost, without considering the decorated coffee cost. This way, the espresso shot is gonna cost 0+.55 I think....
Or am i missing anything?
Nice Tutorial by the way! Cheers!
Antonio
4 years late but whatever. The first instance of the coffee "BaseCoffee" has a price of 1.50, and when you decorate it with the espresso you add .55 to that, totaling 2.05. As far as I know you will always need an instance if ICoffee in order to create a espresso, so you can't just instanciate an espresso by itself.
Yes like he said it’s an onion and each layer is changing the previous value.
Very very nice design patterns series ... Very nice real life examples and explanation by Philip .. thanks for posting such informative vedio .. plz post more designs patterns vedio
Fantastic video. Thank you!
How is the coffe example a decorator example and not a composite?
I like these 2 doing videos.
nice info guy's but maybe next time get a maybe a diagram , or even some uml schematic .. just the code allone makes it hard to follow Judith Bishop did a nice book on the subject years ago "C# 3.0 Design Patterns" published by O'Reilly
Hard disagree. Everybody else puts up Visio slides labelled A and B, while these two have a CONVERSATION and talk with their hands. It's brilliant, and easy to follow, for me at least.
Thank you, very clear.
I couldn't find the link to the design pattern playlist, could someone please link? Thank you!
Edit: Found it th-cam.com/play/PLT2NrqLzZng3YMek58eVZVkBiW3NyVSef.html
thanks
It would be really helpful if you guys could make a video on Code to interface and unity framework(ioc) topics
Thanks, very well explained.
Subsystem for the particula functionality, in short
Oh, ok, so the decorator pattern is something similar to the ECS
Guys, that's gonna mount to an ungodly amount of classes... @_@ I'm getting dizzy.
I didn't understand fully
JS has no types. It means, decorator pattern doesn't apply because all the abstraction for flexible design is available without interfaces or abstract base. That being said, how would author claim that if he knew decorator pattern, it would save lots of time etc in his JS project. This is nonsense
Because everyone decorates an onion. Facepalm.
Console Visualizing Data Transmission Portorate Bypass Polar Design Pattern
if 0 else 0 function 0/00 Point Position Power 0^0/00 Omega
Clock Signature ‰ Com Theta.