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

API changes and support for GLFW 3.1 features. #65

Closed
wants to merge 128 commits into from
Closed

Conversation

dmitshur
Copy link
Member

@dmitshur dmitshur commented Jun 8, 2014

This PR contains changes from the devel branch. That includes minor API changes that make the API easier to use and more idiomatic, as well as support for new features of GLFW 3.1. See changelog in README for a complete list of changes.

It is planned to be merged into master when GLFW 3.1 is released.

Closes #40.
Closes #8.
Closes #56.
Closes #106.

@tapir
Copy link
Member

tapir commented Jun 9, 2014

@shurcooL Looks good. Thanks for this. I think we can delete devel branch now.

@dmitshur
Copy link
Member Author

dmitshur commented Jun 9, 2014

Great, I've deleted devel branch.

Really looking forward for 3.1 to come out so we can press that big green button and close 3 issues at once! :D

@tapir
Copy link
Member

tapir commented Jun 9, 2014

Me too,
looks like it's only 60% complete though: http://www.glfw.org/

@dmitshur
Copy link
Member Author

dmitshur commented Jun 9, 2014

Yeah, I'll try to see if I can lend a hand fixing open issues there, as @elmindreda has a lot of work cut out.

@dmitshur
Copy link
Member Author

image

70% now!

tapir and others added 6 commits June 25, 2014 08:49
Add glfwSetCharModsCallback() support.
changelog updated
Use more idiomatic style for comments, which includes a space after the
//. See
https://code.google.com/p/go-wiki/wiki/CodeReviewComments#Comment_Senten
ces.
Remove references to LockOSThread Wiki example; simply mention
runtime.LockOSThread() in README instead.
Other than docs, there are no code or behavior changes.
Fix missing runtime.LockOSThread() in example code.
Improve documentation style slightly.
@slimsag
Copy link
Member

slimsag commented Jan 20, 2015

I'm beginning work on #118: until I have a PR in for that please don't work on anything except the README to avoid collision as that change will likely touch every .go file in various places.

slimsag and others added 11 commits January 20, 2015 15:39
For details about this solution see the documentation for acceptError,
panicError, and issue #118.
This allows for the explicitly choosing to use the OpenGL ES 2 client
instead of the standard OpenGL client on Desktop (386, amd64) platforms.

To explicitly choose the OpenGL ES 2 client, use the build tag "gles2".
@dmitshur
Copy link
Member Author

I've finally updated all my code to the latest commit on this branch, including API changes. It was definitely a win and made my user code simpler/shorter by removing panic(err), mustBool, mustAction and , _ things.

At this time, I did not run into any instances where the removed error from API presented a problem. Thanks a lot to @slimsag for doing that PR #121!

I'll keep testing it over the next few days and report any issues I notice.

Allow use of OpenGL ES 2 on Desktop platforms with -tags=gles2
@mbertschler
Copy link

Sorry to bother you but is this ready to be merged yet or is there still some work to do?

(Just asking because I am using a glfw version with a manually patched v3.1 feature in a personal project for half a year and I would love to switch to the official package)

@tapir
Copy link
Member

tapir commented Feb 17, 2015

@mbertschler should be any day now. one issue left to resolve #123

@mbertschler
Copy link

@tapir Thank you!
I am really looking forward to switch to the official 3.1 which makes it possible to open source my package, because I don't want people to have to use a patched version of 3.0 just for this tool.
My package tries to provide a cross platform GUI that should make GUI programs as easy to write as a web app. (The programming model is based on React.js.)

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