Lyle, this is a request.
Can you make the gems like fxruby12, fxruby14, fxruby16 so users that choose to use FXRuby 1.2 (for example) won’t be asked to choose which gem to install every time they do ‘gem update’ and they don’t have fox 1.4 installed. I am stumbled with this problem.
Thank you in advance
May 30th, 2006 at 12:38 am
Laurent Julliard:
Great work, Lyle. As a matter of fact I tried to build fox 1.2 on my new Fedora core 5 machine and it fails miserably with compile errors So It tells me that it is time for FreeRIDE to switch from Fox/FXRuby 1.2 to 1.6. By any chance, have you put together a one page document that explain the main changes between between 1.2 or 1.4 and 1.6 like you did once in the past for an older version?
Reza, I’m not sure if the solution is to use different gem names, but I agree that there’s a problem. There was a pretty substantial set of API changes between FOX versions 1.0 and 1.2, and that’s what prompted the original name change. There’s much less breakage due to API incompatibilities between 1.2 and 1.4, and 1.4 and 1.6, however, and I’d like to find a way to get things back to a more uniform naming structure.
In short, this is something I’m thinking about and hope to find a suitable solution for.
Laurent, I am surprised that FOX 1.2 failed to compile under FC5 and that’s probably something that should be brought up on the FOX Users’ mailing list. Having said that, I agree that it’s a good idea to be looking at migrating FreeRIDE to the latest FXRuby.
I never wrote-up a “What’s New” for FOX 1.4, and wasn’t planning to do so for FOX 1.6 either. It’s not that I don’t think those things are useful, it’s just that I don’t have as much as time as I used to to devote to FXRuby and other open source projects. I was really hoping that someone else would have picked up the ball on that project (the “What’s New” docs) but that unfortunately hasn’t happened.
Lyle, this is a request.
Can you make the gems like fxruby12, fxruby14, fxruby16 so users that choose to use FXRuby 1.2 (for example) won’t be asked to choose which gem to install every time they do ‘gem update’ and they don’t have fox 1.4 installed. I am stumbled with this problem.
Thank you in advance
May 30th, 2006 at 12:38 amGreat work, Lyle. As a matter of fact I tried to build fox 1.2 on my new Fedora core 5 machine and it fails miserably with compile errors
So It tells me that it is time for FreeRIDE to switch from Fox/FXRuby 1.2 to 1.6. By any chance, have you put together a one page document that explain the main changes between between 1.2 or 1.4 and 1.6 like you did once in the past for an older version?
Thanks again for the hard work.
May 31st, 2006 at 1:31 pmReza, I’m not sure if the solution is to use different gem names, but I agree that there’s a problem. There was a pretty substantial set of API changes between FOX versions 1.0 and 1.2, and that’s what prompted the original name change. There’s much less breakage due to API incompatibilities between 1.2 and 1.4, and 1.4 and 1.6, however, and I’d like to find a way to get things back to a more uniform naming structure.
In short, this is something I’m thinking about and hope to find a suitable solution for.
Laurent, I am surprised that FOX 1.2 failed to compile under FC5 and that’s probably something that should be brought up on the FOX Users’ mailing list. Having said that, I agree that it’s a good idea to be looking at migrating FreeRIDE to the latest FXRuby.
I never wrote-up a “What’s New” for FOX 1.4, and wasn’t planning to do so for FOX 1.6 either. It’s not that I don’t think those things are useful, it’s just that I don’t have as much as time as I used to to devote to FXRuby and other open source projects. I was really hoping that someone else would have picked up the ball on that project (the “What’s New” docs) but that unfortunately hasn’t happened.
May 31st, 2006 at 2:08 pm