Bridge Pattern Implemented with views.py and iDataResource.py #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented a Bridge Pattern to try and extend the approach how graphs can be displayed in a various formats.
created multiple views(concrete) to display multiple types of graphs(concrete)
This allows less class building and more cardinality among the bridge pattern classes, which can allow a range of graph types(pie, bar, etc) to be viewed in multiple ways (complete, extended, quick, etc).
This will avoid, having to create multiple individual classes, for example, a single class that has a bar graph with a quick view, and another class for a bar graph with an extended view.
This Bridge Pattern will instead "bridge" each concrete view with each concrete graph type for less class building and more flexibility.