add patterns elemenents

behavioral/chain/README.md

@@ -1,5 +1,11 @@
 # Chain of responsibility
 
+## Elements
+
+ - Handler
+ - RequestHandler
+ - Client
+
 ## Description
 
 It consists of a source of command objects and a series of processing objects.

behavioral/mediator/README.md

@@ -1,5 +1,11 @@
 # Behavioral » Mediator
 
+## Elements
+
+ - Mediator
+ - Concrete Mediator
+ - Colleague Class
+
 ## Description
 
 It defined an object that encapsulate the manner of how a set of objects

behavioral/memento/README.md

@@ -1,5 +1,11 @@
 # Behavioral » Memento
 
+## Elements
+
+ - Memento
+ - Originator
+ - Caretaker
+
 ## Description
 
 The memento pattern provides the ability to restore an object to of its

behavioral/observer/README.md

@@ -1,5 +1,12 @@
 # Behavioral » Observer
 
+## Elements
+
+ - Observable
+ - ConcreteObservable
+ - Observer
+ - ConcreteObserver
+
 ## Description
 
 This pattern uncouple an event from its possible handlers. It is useful to

concurrency/pipeline/README.md

@@ -1,5 +1,13 @@
 # Concurrency » Pipeline
 
+## Elements
+
+ - Visitor
+ - ConcreteVisitor
+ - Visitable
+ - ConcreteVisitable
+ - ObjectStructure
+
 ## Description
 
 A pipeline consists of a chain of elements arranged so that the output of each

creational/abstract_factory/README.md

@@ -1,5 +1,13 @@
 # Creational » Abstract Factory
 
+## Elements
+
+ - AbstractFactory
+ - ConcreteFactory
+ - AbstactProduct
+ - Product
+ - Client
+
 ## Description
 
 The difference from factory design pattern is that with this pattern it is possible to manage complex data type.

creational/builder/README.md

@@ -1,5 +1,12 @@
 # Creational » Builder
 
+## Elements
+
+ - Builder
+ - ConcreteBuilder
+ - Director
+ - Product
+
 ## Description
 
 The Builder is a pattern used to build objects. Objects in go can be created with just {}. But in Go is possible to create objects composed by other objects. This is really idiomatic in go, as it doesn't support inheritance.

creational/prototype/README.md

@@ -1,5 +1,11 @@
 # Creational » Prototype
 
+## Elements
+
+ - Client
+ - Prototype
+ - ConcretePrototype
+
 ## Description
 
 With this pattern, is used an already created instance of some type to clone it and complete it with the particular needs of each context. Objects to clone are created at compilation time and can be cloned as many times it is needed at runtime.

structural/bridge/README.md

@@ -1,4 +1,13 @@
 # Bridge
 
+## Elements
+
+ - Abstraction
+ - AbstractionImplementation
+ - Implementor
+ - ConcreteImplementor
+
+## Description
+
 This design pattern is used to "decouple an abstraction from its implementation so that the two can vary independently". The bridge uses encapsulation, aggregation, and can use inheritance to separate responsibilities into different classes.
 

structural/composite/README.md

@@ -1,3 +1,12 @@
 # Composite
 
+## Elements
+
+ - Component
+ - Leaf
+ - Composite
+ - Client
+
+## Description
+
 In software engineering, the composite pattern is a partitioning design pattern. The composite pattern describes a group of objects that is treated the same way as a single instance of the same type of object. The intent of a composite is to "compose" objects into tree structures to represent part-whole hierarchies. Implementing the composite pattern lets clients treat individual objects and compositions uniformly.

structural/flyweight/README.md

@@ -2,7 +2,10 @@
 
 ## Elements
 
-*to do*
+ - Flyweight
+ - ConcreteFlyweight
+ - FlyweightFactoy
+ - Client
 
 ## Dscription
 

structural/proxy/README.md

@@ -4,7 +4,7 @@
 
  - Proxy
  - RealSubject
- - Client
+ - Subject
 
 ## Description