Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider splitting OpenTK dependent classes #320

Open
tomrijnbeek opened this issue Apr 26, 2023 · 0 comments
Open

Consider splitting OpenTK dependent classes #320

tomrijnbeek opened this issue Apr 26, 2023 · 0 comments
Labels
discussion-needed Issue that is not ready for implementation, but still requires discussion enhancement

Comments

@tomrijnbeek
Copy link
Member

🆙 Improvement proposal

Currently the library depends on OpenTK in a variety of places. However, many of its utilities stand by themselves and don't necessarily need to require OpenTK. Therefore it would be interesting to move all the OpenTK dependencies to a separate Bearded.Utilities.OpenTK package, so that choosing to include all of OpenTK in your project becomes optional (also, a Bearded.Utilities.Unity3D package could be considered mirroring the types for Unity).

Context

This should be considered in the context of #294 where we split off SpaceTime into a separate package, which then in turn would make sense to switch to System.Numerics types as underlying types (see #146).

@tomrijnbeek tomrijnbeek added enhancement discussion-needed Issue that is not ready for implementation, but still requires discussion labels Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion-needed Issue that is not ready for implementation, but still requires discussion enhancement
Projects
None yet
Development

No branches or pull requests

1 participant