Skip to main content

Composite Pattern

Composite Pattern 


Gamma Categorization: Structural Design Pattern
Summary: Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.

Sample Code

Problem: We want to store a trips photoset hierarchy.

Code

public abstract class Photo
{
    protected string name;

    public Photo(string name)
    {
        this.name = name;
    }

    public abstract void Add(Photo p);
    public abstract void Remove(Photo p);
    public abstract void Display(int depth);
}

public class SinglePhoto : Photo
{
    public SinglePhoto(string name) : base(name) { }

    public override void Add(Photo p) => Console.WriteLine("Cannot add to a leaf");

    public override void Remove(Photo p) => Console.WriteLine("Cannot remove from a leaf");

    public override void Display(int depth)
    {
        Console.WriteLine(new String('-', depth) + name);
    }
}

public class PhotoSet : Photo
{
    private List<Photo> _children = new List<Photo>();

    public PhotoSet(string name) : base(name) { }

    public override void Add(Photo p) => _children.Add(p);

    public override void Remove(Photo p) => _children.Remove(p);

    public override void Display(int depth)
    {
        Console.WriteLine(new String('-', depth) + name);
        foreach (Photo i in _children)
        {
            i.Display(depth + 2);
        }
    }
}

Usage

var lisbonPhotoSet = new PhotoSet("Trip to Lisbon");

lisbonPhotoSet.Add(new SinglePhoto("Belém Tower"));

var alfamaPhotoSet = new PhotoSet("Alfama area");
alfamaPhotoSet.Add(new SinglePhoto("Se Cathedral"));
alfamaPhotoSet.Add(new SinglePhoto("Portas do Sol"));
alfamaPhotoSet.Add(new SinglePhoto("Lisbon Castle"));
alfamaPhotoSet.Add(new SinglePhoto("Casa dos Bicos"));

lisbonPhotoSet.Add(alfamaPhotoSet);

lisbonPhotoSet.Add(new SinglePhoto("Jerónimos Monastery"));

lisbonPhotoSet.Display(0);


Output

 Trip to Lisbon
--Belém Tower
--Alfama area
----Se Cathedral
----Portas do Sol
----Lisbon Castle
----Casa dos Bicos
--Jerónimos Monastery

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