Make OpenGL.Net portable by decoupling from WinForms #13
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.
Technically, there's no reason for OpenGL.Net to be coupled into WinForms, however, it seemed to have been using
Control
from WinForms through, when it was completely unnecessary. TheHandle
asIntPtr
could be directly passed through, and can be completely decoupled from WinForms.These changes allow it to be used in environments without WinForms. Eg: Here's an example of that uses
WinApi
, a raw C# wrapper to the Win32 API. So, it provides a much simpler model without the overhead of WinForms.Sample: https://github.com/prasannavl/WinApi/blob/master/Samples/Sample.OpenGL/Program.cs
Note: However, since GLControl still is in the same project, WinForms dependency is still brought along. Separating it into a different project could be further done to drop the dependency completely.