Proposal: Reboot go-gl/examples, be more selective.

[Dmitri Shuralyov]

Can we move `go-gl/examples` to `go-gl-legacy/examples`, and then carefully extract 1-2 working, up to date, maintained examples back to `go-gl/examples`.

I can volunteer to update and maintain 2 examples that use latest glfw and OpenGL 2.1, OpenGL 4.1. (currently located in https://github.com/go-gl/examples/tree/master/glow)

In fact, I've already done so, please take a look at:

https://github.com/shurcooL/new-go-gl-examples

https://github.com/shurcooL/new-go-gl-examples/tree/master/glfw31-gl41core-cube#cube

https://github.com/shurcooL/new-go-gl-examples/tree/master/glfw31-gl21-cube#cube

It's a start. The README can be elaborated. Code can (and will be) cleaned up even more. But it works, it compiles, and has a green Travis passing test.

Motivation

I was reading https://sourcegraph.com/blog/live/gopherconindia/112025389257 today (from https://twitter.com/srcgraph/status/570692110430683136), and when I saw the OpenGL section, my heart sank seeing old, GLFW 3.0 using code that doesn't even compile being shown (the source is coming from current go-gl/examples repo). After all the work we've put in in gl and glfw libraries, this is a really poor presentation. I can imagine someone seeing that for the first time being excited, trying to download/find example and seeing the current examples repo, which has lots of things, and they don't even compile.

In the case of examples, I think quality is much more important than quantity. For a beginner, seeing more examples that are poorly organized is a bad thing because they'll not know where to start, and it will appear more complex. For us the developers/maintainers, seeing that many examples that are poorly maintained... it's hard to keep them maintained and full of high quality latest code.

That's why I propose we do the reboot, move current examples repo out of the way, and start with a few simple, working, high quality code examples (and be selective about what we accept into the repo, it shouldn't just be a dump of code without expectation of keeping it updated).

The current go-gl/examples repo was last updated on Sep 7, 2014 and I don't think it will get better, which is why I think doing this is the best course of action (and can be done today).

[Stephen Gutekanst]

A big +1 from me!

I believe with the recent changes that none of those examples build anymore -- and we don't have anyone who has the time to maintain them.

I feel like modifying the existing repository (removing everything, adding back the ones you want to keep/maintain) would be better from history sake -- but either way LGTM.

Cheers,

Stephen

[Dmitri Shuralyov]

+1 to Stephen's suggestion. Minor change to my proposal, instead of moving existing repo to go-gl-legacy, let's just clear it (everything still available in git history), and then we can make PRs to bring back working, maintained examples.

Remember, these are examples, and more is not better. Fewer better examples is better.

[Dmitri Shuralyov]

Ok, I will clear the repo (preserving git history) and make a PR that adds my 2 examples).

Let's go with PRs and accept PRs only if it's reasonable expectation that the contributed examples will be well maintained.

On Wednesday, February 25, 2015 at 8:58:00 PM UTC-8, Jrago...@gmail.com wrote:

Yes just clear it. In fact, I think the glexamples ones still point to the old Jragonmiris/mathgl repository instead of the current one.

--
You received this message because you are subscribed to the Google Groups "go-gl OpenGL libraries for go" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-gl+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sri Gogineni]

Thanks! As someone who is learning Open GL, the quality maintained examples that works was much more helpful to learn from than many non-working demos.

I'm currently working through Open GL ES tutorials and noticed a lack of GL ES examples. Would you be open to a PR or is that solely the domain of golang.org/x/mobile?

[Harry Ayres]

I've just started going through opengl-tutorial.org and found the examples now in the repository invaluable in translating from C++ to Go. Thanks so much for offering that clarity.

I'm probably going to make the Go version of the tutorial code public in my own git repo.