Closed ashes999 closed 11 years ago
The main reason behind the name changing was that, when I uploaded gosu_android as a gem, then name gosu was already taken. So I named the gem gosu_android, in the documentation they advice you to name consistently to avoid problems and I wanted to push the gem as soon as possible.
Anyway I agree with you, so I'll do some testing on how this works, so it can be reverted to its previous state.
As a side note, in the garble image issue you pointed out, that gosu_android is currently alpha-ish. Again you are right. In fact I wouldn't event say it is in alpha. So even thought I am quite happy that some one is using it, bare in mind that I don't think the code is ready for any real application. Furthermore this is the first "big" application I've ever done, I am just a student and gosu_android is my final degree project :-)
Okay, I would go with what rubygems says. Those guys have a lot of experience and wisdom behind their recommendations; this is a pretty small thing, all things considered.
As for you being a student ... that's hilarious. Big, awesome projects (see: Ruboto, mruby, mobiruby, etc.) all come down to one person. I'm glad you're working hard on it -- solving real problems, interacting with real customers/users (me).
I only hope you'll keep supporting it after your project, because I intend to make at least one (hopefully/maybe more) games out of it, and I can't make too much sense out of the code base :)
Which means I may report more issues -- but hopefully not. I almost have everything I need for my "proof of concept:" showing images, playing audio, and handling clicks.
:+1:
Hi,
I've been dabbling with gosu_android for a while. I'm planning on making a cross-platform (Windows + Android) app with Gosu + Gosu Android.
In the past, I could use
require 'gosu'
, and it would work across platforms. Now, I need:I protest! I'm sure you changed this for a very good reason; what was it, and would you consider reverting this back to the old behaviour?