Bridge Pattern - consequences

Author: tk-codes

README.md

@@ -22,7 +22,7 @@ Design Patterns in C# / .NET
 | | Pattern | 
 |---|--- | 
 |:heavy_check_mark:| [Adapter](/StructuralPatterns/Adapter) | 
-| | Bridge | [Bridge](/StructuralPatterns/Bridge) |
+| | [Bridge](/StructuralPatterns/Bridge) |
 |:heavy_check_mark: | [Composite](/StructuralPatterns/Composite) | 
 |:heavy_check_mark:| [Decorator](/StructuralPatterns/Decorator) | 
 |:heavy_check_mark:| [Facade](/StructuralPatterns/Facade) | 

StructuralPatterns/Bridge/BasicRemote.cs

@@ -0,0 +1,32 @@
+using System;
+using System.Collections.Generic;
+using System.Linq;
+using System.Text;
+using System.Threading.Tasks;
+
+namespace StructuralPatterns.Bridge
+{
+    public class BasicRemote : IRemote
+    {
+        
+        public void PowerOn()
+        {
+            throw new NotImplementedException();
+        }
+
+        public void PowerOff()
+        {
+            throw new NotImplementedException();
+        }
+
+        public void VolumeUp()
+        {
+            throw new NotImplementedException();
+        }
+
+        public void VolumeDown()
+        {
+            throw new NotImplementedException();
+        }
+    }
+}

StructuralPatterns/Bridge/IDevice.cs

@@ -0,0 +1,16 @@
+using System;
+using System.Collections.Generic;
+using System.Linq;
+using System.Text;
+using System.Threading.Tasks;
+
+namespace StructuralPatterns.Bridge
+{
+    public interface IDevice
+    {
+        void PowerOn();
+        void PowerOff();
+        int GetVolumen();
+        void SetVolume();
+    }
+}

StructuralPatterns/Bridge/IRemote.cs

@@ -0,0 +1,19 @@
+using System;
+using System.Collections.Generic;
+using System.Linq;
+using System.Text;
+using System.Threading.Tasks;
+
+namespace StructuralPatterns.Bridge
+{
+    // Abstraction
+    public interface IRemote
+    {
+        void PowerOn();
+        void PowerOff();
+        void VolumeUp();
+        void VolumeDown();
+    }
+
+
+}

StructuralPatterns/Bridge/README.md

@@ -25,9 +25,20 @@ This enables to configure an `Abstraction`(Interface) with an `Implementor`(Inte
 
 ## Benefits
 
+* Decouples an implementation so that it is not bound permanently to an interface.
+* Abstraction and implementation can be extended independently.
+* Changes to the concrete abstraction classes don't affect the client.
+* Allows building platform independent code
+* Hides the implementation details from client
 
 ## Drawbacks
 
+* Increases overall code complexity by creating multiple additional classes.
+
+## Known Uses
+
+* Useful in graphic and windowing systems that need to run over multiple platforms
+* Useful any time you need to vary an interface and an implementation in different ways
 
 ## Common Structure
 
@@ -43,7 +54,11 @@ This enables to configure an `Abstraction`(Interface) with an `Implementor`(Inte
 * ConcreteImplementor
   * implements the `Implementor` interface.
 
-_[Source: http://www.dofactory.com/net/memento-design-pattern]_
-
 ## Example
 
+// TODO
+
+## Comparison with other patterns
+
+* **Adapter** makes the unrelated classes work together. Adapter makes things work after they're designed; Bridge is designed beforehand to let the abstraction and implmentation vary independently. *[GoF, p219]*
+