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

C# Extension Methods

 C# Extension Methods Extension methods      public   static   class   ExtensionMethods     {          public   static   Stopwatch   Measure ( this   Func < int >  f )         {              var   sw  =  new   Stopwatch ();              sw . Start ();              f ();              sw . Stop ();              return   sw ;         }          public   static   void   Save ( this   ISerializable   s...
Post a Comment
Read more

SOLID (4/5) - Interface segregation principle

Interface segregation principle In the field of software engineering, the interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them. Such shrunken interfaces are also called role interfaces. ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy. using   System ; namespace   interfacesegregation {      public   class   Document       {     }      public   interface   IMachine       {          void   Print ( Document   d );          void   Scan ( Document   d );     ...
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