This link has been bookmarked by 38 people . It was first bookmarked on 13 Aug 2006, by aj.
-
10 Dec 14
-
The abstract factory pattern provides a way to encapsulate a group of individual factories that have a common theme without specifying their concrete classes
-
-
-
29 Oct 14
-
20 Aug 14
-
-
This insulates client code from object creation by having clients ask a factory object to create an object of the desired abstract type and to return an abstract pointer to the object.[4]
-
The client code has no knowledge whatsoever of the concrete type, not needing to include any header files or class declarations related to it. The client code deals only with the abstract type. Objects of a concrete type are indeed created by the factory, but the client code accesses such objects only through their abstract interface.[5]
-
The different factory then creates objects of a different concrete type, but still returns a pointer of the same abstract type as before — thus insulating the client code from change
-
-
-
17 Dec 13
-
the client software creates a concrete implementation of the abstract factory and then uses the generic interface
-
-
08 Nov 13
-
encapsulate a group of individual factories
-
without specifying their concrete classes
-
common theme
-
-
07 Oct 13
-
way to encapsulate a group of individual factories that have a common theme without specifying their concrete classes
-
lient software creates a concrete implementation of the abstract factory
-
normal usage
-
client does not know
-
which concrete objects it gets from each of these internal factories
-
nly the generic interfaces of their products
-
eparates the details of implementation of a set of objects from their general usage
-
provides interfaces to create a number of products
-
abstract factory class
DocumentCreator -
example
-
system would have any number of derived concrete versions of the
DocumentCreatorclass likeFancyDocumentCreatororModernDocumentCreator, -
createResume()
-
createLetter()
-
ach with a different implementation of
createLetter()andcreateResume() -
-
-
-
resulting objects would be created from the same
DocumentCreatorimplementation -
would share a common theme (they would all be fancy or modern objects).
-
client would only need to know how to handle the abstract
LetterorResumeclass, not the specific version that it got from the concrete facto -
makes it possible to interchange concrete implementations without changing the code that uses them
-
may result in unnecessary complexity and extra work in the initial writing of code
-
-
27 Jul 13
-
insulates client code from object creation by having clients ask a factory object to create an object of the desired abstract type and to return an abstract pointer to the object
-
The client code has no knowledge whatsoever of the concrete type, not needing to include any header files or class declarations related to it.
-
Adding new concrete types is done by modifying the client code to use a different factory, a modification that is typically one line in one file
-
-
-
30 Mar 13
-
16 Jan 13
-
13 Jul 12
-
Abstract factory pattern
-
-
18 Jun 12
-
Abstract factory pattern
-
Example
-
/* GUIFactory example -- */
-
-
15 Apr 11
-
10 Mar 10
-
20 May 09
pilgrim78A 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 us
-
24 Nov 08
-
04 Aug 08
-
13 May 08
-
09 Aug 07
-
19 Jul 07
-
10 May 07
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.