Design Patterns discussion

["Silva, Lionel" <lisilva AT inovant.com>]

remove

-----Original Message-----
From: gang-of-4-patterns-bounces AT cs.uiuc.edu [mailto:gang-of-4-patterns-bounces AT cs.uiuc.edu]On Behalf Of Mandar Nanivadekar
Sent: Thursday, December 02, 2004 3:49 AM
To: gang-of-4-patterns AT cs.uiuc.edu
Subject: Re: Re: [gang-of-4-patterns] Design pattern is GDI

I was doing some more thinking on this problem yesterday.
Could it be a Bridge.
The Device pattern is an abstraction?
Some more methods could be added.
So this abstraction is varying and the implmentation may vary as well.

The device driver side of the GDI could be implemented by abstract factory.


On Wed, 01 Dec 2004 jdeena AT comcast.net wrote :
>I guess it would be builder(creational) or template pattern(behavior) if you have to implement any of  abtract operations from GDI or it could be command pattern if you have to override any super class operations.
>
>-------------- Original message --------------
>
>Hello all,
>
>I have a question.
>GDI in windows is a device driver abstraction.
>The client programmer does not know which device he is programming to.
>It may be a display or a printer etc.
>GDI hides all this,
>and chooses the device driver currently installed on the machine.
>The device driver written for windows has to conform to a particular interface. Hence GDI can work with any device.
>
>Which design pattern is this?
>Is it a factory?
>
>Rgds,
>Mandar
>
>
>>_______________________________________________
>gang-of-4-patterns mailing list
>gang-of-4-patterns AT cs.uiuc.edu
>http://mail.cs.uiuc.edu/mailman/listinfo/gang-of-4-patterns