Skip to main content

Decorator Pattern

Decorator Pattern 


Gamma Categorization: Structural Design Pattern
Summary: Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.

Sample Code

Problem: We want extend our Camera object in order to allow it to use LiveView in addiction to taking photos.

Code

public abstract class Camera
{
    public string Name { get; set; }

    public abstract void TakePhoto();
}

public class DigitalCamera : Camera
{
    public override void TakePhoto() => System.Console.WriteLine($"Taking a photo with a {Name}.");
}


public abstract class AdvancedCamera : Camera
{
    public Camera Camera { get; protected set; }

    public AdvancedCamera(Camera camera) 
    {
        Camera = camera;
    }

    public abstract void LiveView();
}

public class AdvancedDigitalCamera : AdvancedCamera
{
    public AdvancedDigitalCamera(Camera camera) : base (camera) { }

    public override void TakePhoto() => Camera.TakePhoto();

    public override void LiveView() => System.Console.WriteLine($"Using LiveView in a {Camera.Name}.");
}

Usage

var camera = new AdvancedDigitalCamera(new DigitalCamera { Name = "Canon 70D" });
camera.TakePhoto();
camera.LiveView();

Output

Taking a photo with a Canon 70D.
Using LiveView with a Canon 70D.


Comments

Post a Comment

Popular posts from this blog

XML Webservice (ASMX) - SOAP Request and Response Invocation logging

You are an integration developer. Eventualy you came into the state where there is nothing else you can debug, and you have to check which SOAP request it is built on the request, and which SOAP response you are getting from the server. C# XML Webservice (ASMX) - SOAP Request and Response Invocation logging In the legaccy .NET framework System.Web.Services , this means using soapExtensions to help you intersept the interaction with the webservice. This is done like so:  public class TraceExtension : SoapExtension     {         Stream oldStream;         Stream newStream;         string filename;         // Save the Stream representing the SOAP request or SOAP response into          // a local memory buffer.          public override Stream ChainStream(Stream stream)         {           ...
Post a Comment
Read more

Abstract Factory Pattern

Abstract Factory Pattern  Gamma Categorization: Creational Design Patten Summary: When the object construction is complicated, needing multiple arguments, we should create a separate function (Factory Method) or class (Factory), which is responsible for the creation of the all object. Problem examples Suport of multiple databases Multiple data sources: Serial port, ethernet port, device driver Diferent report types Solution Abstract class Generalized interface A Factory creates instances of the concrete classes Sample Code The abstract factory public   interface   IPhotoFactory {      IAnaloguePhoto   CreateAnaloguePhoto ();      IDigitalPhoto   CreateDigitalPhoto (); } The abstract products public   interface   IAnaloguePhoto {      string   GetName (); } public   interface   IDigitalPhoto {      ...
Post a Comment
Read more

SOLID (1/5) - Single Resposibility Principle

 SOLID (1/5) - Single Resposibility Principle The single-responsibility principle (SRP) is a computer-programming principle that states that every class in a computer program should have responsibility over a single part of that program's functionality, which it should encapsulate. All of that module, class or function's services should be narrowly aligned with that responsibility. In the following example we have a TodoList class which only handles it's own functionality logic, and then we have a Persistance class which handles the saving logic, hence keeping the concerns separeted. using   System ; using   System . Collections . Generic ; namespace   Journal {      public   class   TodoList     {          private   readonly   List < string >  _entries  =  new   List < string >();          private...
Post a Comment
Read more