Timeline for Observer design pattern in Swift
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2016 at 1:40 | vote | accept | Reza Shirazian | ||
| Apr 13, 2016 at 22:13 | comment | added | Reza Shirazian | I agree that the subscribe/unsubscribe should be taken out of the observer protocol, there is no need to enforce a specific way for the observer to deal with the property change. I also understand your point that having a MechanicObserver is overkill and somewhat FizzBuzzEnterprise-like but this is part of a series of article I'm writing on design patterns and I made up the problem just so I can solve it using the observer pattern. Also thank you for taking the time and reviewing my code, I'm going to heed your advice and rethink some of my approaches. | |
| Apr 13, 2016 at 2:07 | history | answered | nhgrif | CC BY-SA 3.0 |