Skip to main content

Visitor Pattern

Visitor Pattern 


Gamma Categorization: Behavioral Design Pattern
Summary: 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.

Sample Code

Problem: We want to correct photo filters based on the camera brand

Code

public abstract class Element
{
    public abstract void Accept(IVisitor visitor);
}

public class Filter : Element
{
    public string Name { get; set; }
    public double Exposure { get; set; }
    public double Contrast { get; set; }
    public double Saturation { get; set; }

    public Filter(string name, double exposure, double contrast, double saturation)
    {
        this.Name = name;
        this.Exposure = exposure;
        this.Contrast = contrast;
        this.Saturation = saturation;
    }

    public override void Accept(IVisitor visitor)
    {
        visitor.Visit(this);
    }
}

public class Filters
{
    private List<Filter> _filters = new List<Filter>();

    public void Attach(Filter filter)
    {
        _filters.Add(filter);
    }

    public void Detach(Filter filter)
    {
        _filters.Remove(filter);
    }

    public void Accept(IVisitor visitor)
    {
        foreach (Filter f in _filters)
        {
            f.Accept(visitor);
        }
        Console.WriteLine();
    }
}

public class Impact : Filter
{
    public Impact() : base("Impact", 0, 1, 1) { }
}

public class Burn : Filter
{
    public Burn() : base("Brighten", 1, 0, 0) { }
}

public class Dodge : Filter
{
    public Dodge() : base("Impact", -1, 0, 0) { }
}

public interface IVisitor
{
    void Visit(Element element);
}

public class CanonCorrectionVisitor : IVisitor
{
    public void Visit(Element element)
    {
        Filter filter = element as Filter;
        filter.Exposure *= -1.01;
        filter.Contrast *= 1.01;
        filter.Saturation *= 1.02;

        Console.WriteLine("{0} {1}'s new configuration: exposure {2}, contrast {3}, saturation {4}", 
            filter.GetType().Name, filter.Name, filter.Exposure, filter.Contrast, filter.Saturation);
    }
}

public class NikonCorrectionVisitor : IVisitor
{
    public void Visit(Element element)
    {
        Filter filter = element as Filter;
        filter.Contrast *= 1.02;
        filter.Saturation *= 1.01;

        Console.WriteLine("{0} {1}'s new configuration: exposure {2}, contrast {3}, saturation {4}", 
            filter.GetType().Name, filter.Name, filter.Exposure, filter.Contrast, filter.Saturation);
    }
}

Usage

Filters f = new Filters();
f.Attach(new Impact());
f.Attach(new Burn());
f.Attach(new Dodge());

f.Accept(new CanonCorrectionVisitor());

Output

Impact Impact's new configuration: exposure -0, contrast 1,01, saturation 1,02
Burn Brighten's new configuration: exposure -1,01, contrast 0, saturation 0
Dodge Impact's new configuration: exposure 1,01, contrast 0, saturation 0

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