Next isState
An application doesn't need to always be aware of it's state. Awareness tends to add more complexity into an application (such as multiple conditions). By extracting the different states into separate implementations all that is left for the application to do is update it's state to change it's functionality. A great example is a GPS and how it changes between day navigation and night navigation (by car, foot or bike).
Ready to Level Up Your Skills?
Join thousands of learners on 02GEEK and start your journey to becoming a coding expert today!
Enroll Now for Free!Chain of Responsibility %u2013 Part 1
- Linking objects to each other in a chain. - no central control each link %u201Cdecides%u201D if to continue. - Ideal for complex animations that effect other objects.
06:10
Chain of Responsibility - Part 2
- Decentralized logic making. - Each link can be changed. - A loop can be created as well.
08:55
Observer- adding and dispatching events
- Announcing events without explicit communication. - Event dispatching and listeners. - Building an Event dispatcher Decorator.
09:01
Observer - removing events
- When you want to stop listening. - Important for memory management. - Implementing a fully functional event dispatcher.
04:46
State
- Different states of an application demand different reactions. - The more aware the main object is to the difference the more it needs to think %u2013 conditions. - Extracting the states to separat
14:26