When running gosu-examples in bin/* - outputs errors (added logs)

[gosu]

When running gosu-examples in bin/* - outputs errors (added logs)

[jlnr]

Yeah, that is why I didn't include a Gemfile: these gems break all the time.

I'm not sure what I can do about this issue, other than omitting these examples when their dependencies are not met.

[Juksefantomet]

Oh I can see that.

I'm curious though as this is the example "showcase" for the examples.

Just making a suggestion here but..

Wouldn't it be benefitial to have a pure ruby only gosu - only - examples project. if this is to advocate the usage of gosu it would be neat to see a functional one not using external gems.

And then maybe a gosu-advanced-examples would be more of a "extras included" examples bundle where you would implement such (namely this gosu-examples project)

This would effectively allow you to make a Gemfile with ruby and gosu version locked to a stabile release.

Only in the advanced examples project locked to a stable ruby and gosu release that works in accordance with the additional gems, but with a disclaimer saying those gems are third party and might cause conflicts and such if not adhering to the recommended stabile versions of ruby and gosu.

[jlnr]

Hmmm, to be honest I'm not a fan of this idea. It adds more overhead, and I don't want to fragment a niche project like gosu-examples any further.

A Gemfile would not help users who gem install gosu-examples, except if the gem dependencies were locked to very specific versions. All we really need for pure-Ruby examples is a recent-enough version of Gosu, and the gemspec lets us do this.

And people who download/git-clone the pure-Ruby repository shouldn't have to change their Ruby version to whatever I last pinned in .ruby-version. A Gemfile (without .lock) would let us specify a minimum version of Gosu, but I'm not sure if that alone is worth the extra steps.

The problem with the third-party gems is that I don't think it's viable to create a complex set of rules about Ruby versions, gem versions, and operating systems on which all three gems (OpenGL, Chipmunk, RMagick) will work. And even if that's possible, someone who wants to see the Chipmunk example shouldn't have to jump through the hoops necessary to install the RMagick gem.

The only solution I can think of is to have better error reporting when external gems cannot be loaded. Or we could drop integration examples with fragile libraries altogether. But since Ruby lets us gracefully ignore LoadErrors, why throw code away 🤷‍♂️

Closing this for now. I want to update the UI of gosu-examples some time after the Gosu 1.0 release (so, anytime from next month to 2021... :D). I'll try to improve the error messages when I get to this.

[Juksefantomet]

A Gemfile would not help users who gem install gosu-examples, except if the gem dependencies were locked to very specific versions. All we really need for pure-Ruby examples is a recent-enough version of Gosu, and the gemspec lets us do this.

What you're saying here is exactly what i was pointing out :)

the fragmentation was to separate the two, and pure projects have a recommended ruby version to pin a stable one. that was my only point. the separation of a more advanced one was a suggestion if one wanted to keep the third party unstable packages that cause issues.