Refactor opengl examples to reduce code duplication and fix warnings #7
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.
Glancing over the opengl examples I found a lot of warnings and bad practices: code duplication, non-private fields and various inconsistencies.
I'd like to propose some simple refactorings to clean up the examples. After all, the examples are probably the first thing new developers see.
This pull request is not complete, but I would like to have some feedback on the proposal. The
ImmediateModeDemo
andNoVerticesBSplineDemo
have been refactored as examples. The glfw scaffolding (which is duplicated among all examples) has been extracted into a parent class, so that each example only contains logic and state relevant for the example.