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

Switch from flextGL to gl package. #7

Closed
Noeda opened this issue Dec 9, 2014 · 2 comments · Fixed by #9
Closed

Switch from flextGL to gl package. #7

Noeda opened this issue Dec 9, 2014 · 2 comments · Fixed by #9
Assignees

Comments

@Noeda
Copy link
Owner

Noeda commented Dec 9, 2014

Should not duplicate efforts, no, yes? gl didn't exist when Caramia was started. It would give us the raw bindings and as far as API goes you can use it in a very similar way to the FlextGL way.
https://github.com/ekmett/gl

I'll do this at some point.

@Noeda Noeda self-assigned this Dec 9, 2014
@abbradar
Copy link
Collaborator

I've wanted to ask if channelized-opengl work has been abandoned, looks like this is the answer ^_^.
Looked at the code: they have the same IORef approach as us, just exploit laziness more to avoid flextInit-like function AFAIU. They also have a wrapper for getProcAddress which looks more cross-platform-ey.
An outline to what likely needs to be done:

  • Check needed extensions in withContext; they have corresponding Bools for that.
  • Move getGLVersion inside our code.

Other than that, just resolve naming issues if any and it's done. Looks good!

Upd: we shouldn't even check anything in withContext actually, just use these Bools where needed.

@Noeda
Copy link
Owner Author

Noeda commented Dec 10, 2014

Yeah, I abandoned channelized-opengl. I was going to attempt to hide the fact that you have to do all your OpenGL work in a single bounded thread (by communicating with channels between OpenGL thread and other threads, thus the name). I put a phantom type on everything and it turned out to be a bad idea. Extra safety is nice and I did have re-entrant function pointers but I felt it was not worth the extra type baggage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants