Awesome

DelphiPatterns

This project should represent a complete set of all the GoF design patterns implemented in Delphi.

Originally created by Elector and published to delphipatterns.codeplex.com _{(Archive link)}, but is no longer available there.

Each pattern is implemented in seperate directory/project. The pattern is in the *.pattern.pas file, while the example for it is in the *.example.pas file.

List of patterns

• Behavioral - Most behavioral design patterns are specifically concerned with communication between objects.
  • Chain of Responsibility [Usage] - delegates commands to a chain of processing objects.
  • Command [Usage] - creates objects that encapsulate actions and parameters.
  • Interpreter [Usage] - implements a specialized language.
  • Iterator [Usage] - accesses the elements of an object sequentially without exposing its underlying representation.
  • Mediator [Usage] - allows loose coupling between classes by being the only class that has detailed knowledge of their methods.
  • Memento [Usage] - provides the ability to restore an object to its previous state (undo).
  • Observer [Usage] - a publish/subscribe pattern, which allows a number of observer objects to see an event.
  • State [Usage] - allows an object to alter its behavior when its internal state changes.
  • Strategy [Usage] - allows one of a family of algorithms to be selected on-the-fly at runtime.
  • Template Method [Usage] - defines the skeleton of an algorithm as an abstract class, allowing its subclasses to provide concrete behavior.
  • Visitor [Usage] - separates an algorithm from an object structure by moving the hierarchy of methods into one object.
• Creational - Patterns that create objects, rather than having to instantiate objects directly. This gives the program more flexibility in deciding which objects need to be created for a given case.
  • Abstract Factory [Usage] - groups object factories that have a common theme.
  • Builder [Usage] - constructs complex objects by separating construction and representation.
  • Factory Method [Usage] - creates objects without specifying the exact class to create.
  • Prototype - creates objects by cloning an existing object.
  • Singleton [Usage] - restricts object creation for a class to only one instance.
• Structural - concern class and object composition. They use inheritance to compose interfaces and define ways to compose objects to obtain new functionality.
  • Adapter [Usage] - allows classes with incompatible interfaces to work together by wrapping its own interface around that of an already existing class.
  • Bridge [Usage] - decouples an abstraction from its implementation so that the two can vary independently.
  • Composite [Usage] - composes zero-or-more similar objects so that they can be manipulated as one object.
  • Decorator [Usage] - dynamically adds/overrides behavior in an existing method of an object.
  • Facade [Usage] - provides a simplified interface to a large body of code.
  • Flyweight - reduces the cost of creating and manipulating a large number of similar objects.
  • Proxy [Usage] - provides a placeholder for another object to control access, reduce cost, and reduce complexity.

License

The license is still Common Development and Distribution License (CDDL), the same as the original implementation. According to FOSSA it has similar provisions to the Mozilla Public License 2.0 and the Eclipse Public License.