Tagged: Design Patterns


Phabstractic: Generic Event (Universal Event System)

asherwunk/phabstractic now implements a common event object, useful in the “Universal Event System”. The Universal Event System What I call the universal event system is basically several constructs built on top of the Publisher/Observer design...


Phabstractic: Observer/Publisher Design Pattern

Observers and Publisher design patterns are very important in that they enable a certain amount of reactive programming. When you only want something to execute or occur when a particular event occurs it makes more sense to just test for state change then to hard code in an if clause for every step.


Phabstractic: Abstract Factory Pattern

The abstract factory pattern provides a way to encapsulate a group of individual factories that have a common theme without specifying their concrete classes.


Phabstractic: Singleton Trait Design Pattern

In software engineering, the singleton pattern is a design pattern that restricts the instantiation of a class to one object. This is useful when exactly one object is needed to coordinate actions across the system.