The Abstract Factory of Necromantic Cursors
Summon families of related apparitions without specifying their concrete manifestations.
Summon families of related apparitions without specifying their concrete manifestations.
Convert the interface of a forgotten tomb into another interface clients expect.
Decouple an abstraction from its implementation so that the two can vary independently.
Separate the construction of a complex DBF skeleton from its spectral representation.
Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request.
Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
Compose objects into tree structures to represent part-whole hierarchies of the undead.
Attach additional responsibilities to an apparition dynamically.
Provide a unified interface to a set of interfaces in the necromantic subsystem.
Define an interface for creating an apparition, but let subclasses decide which entity to instantiate.
Use sharing to support large numbers of fine-grained spirits efficiently.
Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly.
Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.
Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
Specify the kinds of apparitions to create using a prototypical instance, and create new spirits by copying this prototype.
Provide a surrogate or placeholder for another object to control access to it.
Ensure a class only has one instance, and provide a global point of access to the undead master.
Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.