Difference between revisions of "Abstract Factory"

From CDOT Wiki
Jump to: navigation, search
(Code Example)
(Code Example)
 
(18 intermediate revisions by the same user not shown)
Line 11: Line 11:
  
 
===Code Example===
 
===Code Example===
 +
'''JAVA'''
 +
<pre>
 +
/*
 +
* GUIFactory example
 +
*/
  
== Java Example ==
+
public abstract class GUIFactory {
 +
  public static GUIFactory getFactory() {
 +
        int sys = readFromConfigFile("OS_TYPE");
 +
        if (sys == 0) {
 +
            return(new WinFactory());
 +
        } else {
 +
            return(new OSXFactory());
 +
        }
 +
  }
 +
  public abstract Button createButton();
 +
}
  
public abstract class CPU {
+
class WinFactory extends GUIFactory {
     ...
+
    public Button createButton() {
} // class CPU
+
        return(new WinButton());
 +
     }
 +
}
  
The concrete widget classes are simply classes that implement the widget interfaces:
+
class OSXFactory extends GUIFactory {
 +
    public Button createButton() {
 +
        return(new OSXButton());
 +
    }
 +
}
  
class EmberCPU extends CPU {
+
public abstract class Button  {
     ...
+
     private String caption;
} // class EmberCPU
+
    public abstract void paint();
 +
   
 +
    public String getCaption(){
 +
        return caption;
 +
    }
 +
    public void setCaption(String caption){
 +
        this.caption = caption;
 +
    }
 +
}
  
Below is code for a concrete factory class that creates instances of classes to test ember architecture computers:
+
class WinButton extends Button {
 +
    public void paint() {
 +
      System.out.println("I'm a WinButton: " + getCaption());
 +
    }
 +
}
  
class EmberToolkit extends ArchitectureToolkit {
+
class OSXButton extends Button {
     public CPU createCPU() {
+
     public void paint() {
        return new EmberCPU();
+
      System.out.println("I'm a OSXButton  : " + getCaption());
     } // createCPU()
+
     }
 +
}
  
     public MMU createMMU() {
+
public class Application {
         return new EmberMMU();
+
     public static void main(String[] args) {
     } // createMMU()
+
         GUIFactory aFactory = GUIFactory.getFactory();
     ...
+
        Button aButton = aFactory.createButton();
} // class EmberFactory
+
        aButton.setCaption("Play");
 +
        aButton.paint();
 +
     }
 +
    //output is
 +
    //I'm a WinButton: Play
 +
    //or
 +
     //I'm a OSXButton: Play
 +
}
 +
</pre>
  
Below is the code for the abstract factory class:
+
'''C++'''
 +
<pre>
 +
#include <memory>
 +
using std::auto_ptr;
  
public abstract class ArchitectureToolkit {
+
class Control { };
    private static final EmberToolkit emberToolkit = new
 
EmberToolkit();
 
    private static final EnginolaToolkit
 
enginolaToolkit
 
      = new EnginolaToolkit();
 
...
 
  
    /**
+
class PushControl : public Control { };
    * Returns a concrete factory object that is an
 
instance of the
 
    * concrete factory class appropriate for the given
 
architecture.
 
    */
 
    static final ArchitectureToolkit getFactory(int
 
architecture) {
 
        switch (architecture) {
 
          case ENGINOLA:
 
            &nbs
 
p; return enginolaToolkit;
 
  
          case EMBER:
+
class Factory {
            &nbs
+
public:
p; return emberToolkit;
+
  // Returns Factory subclass based on classKey.  Each
            ...
+
  // subclass has its own getControl() implementation.
        } // switch
+
  // This will be implemented after the subclasses have
        String errMsg =
+
  // been declared.
Integer.toString(architecture);
+
  static auto_ptr<Factory> getFactory(int classKey);
        throw new
+
  virtual auto_ptr<Control> getControl() const = 0;
IllegalArgumentException(errMsg);
+
};
    } // getFactory()
 
  
    public abstract CPU createCPU() ;
+
class ControlFactory : public Factory {
    public abstract MMU createMMU() ;
+
public:
    ...
+
  virtual auto_ptr<Control> getControl() const {
} // AbstractFactory
+
      return auto_ptr<Control>(new PushControl());
 +
  }
 +
};
  
Client classes typically create concrete widget objects using code that looks something like this:  
+
auto_ptr<Factory> Factory::getFactory(int classKey) {
public class Client {
+
  // Insert conditional logic here.  Sample:
    public void doIt () {
+
  switch(classKey) {
        AbstractFactory af;
+
    default:
        af =
+
      return auto_ptr<Factory>(new ControlFactory());
AbstractFactory.getFactory(AbstractFactory.EMBER);
+
  }
        CPU cpu = af.createCPU();
+
}
        ...
+
</pre>
    } // doIt
 
} // class Client
 
  
 
===Reference===
 
===Reference===

Latest revision as of 19:41, 18 February 2007

Definition

A software design pattern, the Abstract Factory Pattern provides a way to encapsulate a group of individual factories that have a common theme. In normal usage, the client software would create a concrete implementation of the abstract factory and then use the generic interfaces to create the concrete objects that are part of the theme. The client does not know (nor care) about which concrete objects it gets from each of these internal factories since it uses only the generic interfaces of their products. This pattern separates the details of implementation of a set of objects from its general usage.

UML Diagram

Abstract factory uml.gif


Picture sourced:[1]

Code Example

JAVA

/*
* GUIFactory example
*/

public abstract class GUIFactory {
   public static GUIFactory getFactory() {
        int sys = readFromConfigFile("OS_TYPE");
        if (sys == 0) {
            return(new WinFactory());
        } else {
            return(new OSXFactory());
        }
   }
   public abstract Button createButton();
}

class WinFactory extends GUIFactory {
    public Button createButton() {
        return(new WinButton());
    }
}

class OSXFactory extends GUIFactory {
    public Button createButton() {
        return(new OSXButton());
    }
}

public abstract class Button  {
    private String caption;
    public abstract void paint();
    
    public String getCaption(){
        return caption;
    }
    public void setCaption(String caption){
        this.caption = caption;
    }
}

class WinButton extends Button {
    public void paint() {
       System.out.println("I'm a WinButton: " + getCaption());
    }
}

class OSXButton extends Button {
    public void paint() {
       System.out.println("I'm a OSXButton  : " + getCaption());
    }
}

public class Application {
    public static void main(String[] args) {
        GUIFactory aFactory = GUIFactory.getFactory();
        Button aButton = aFactory.createButton();
        aButton.setCaption("Play");
        aButton.paint();
    }
    //output is
    //I'm a WinButton: Play
    //or
    //I'm a OSXButton: Play
}

C++

#include <memory>
using std::auto_ptr;

class Control { };

class PushControl : public Control { };

class Factory {
 public:
   // Returns Factory subclass based on classKey.  Each
   // subclass has its own getControl() implementation.
   // This will be implemented after the subclasses have
   // been declared.
   static auto_ptr<Factory> getFactory(int classKey);
   virtual auto_ptr<Control> getControl() const = 0;
};

class ControlFactory : public Factory {
public:
   virtual auto_ptr<Control> getControl() const {
      return auto_ptr<Control>(new PushControl());
   }
};

auto_ptr<Factory> Factory::getFactory(int classKey) {
  // Insert conditional logic here.  Sample:
  switch(classKey) {
    default:
      return auto_ptr<Factory>(new ControlFactory());
  }
}

Reference

http://en.wikipedia.org/wiki/Abstract_factory_pattern
http://www.dofactory.com/Patterns/PatternAbstract.aspx