On Jun 24, 2008, at 5:27 PM, Eloy Duran wrote:
Also it is now in lib/osx/rubycocoa.rb and there's a osx/cocoa.rb. The latter will probably be removed as to not have RubyCocoa applications work by default. This needs to be discussed further.
As I said earlier I don't think osx/cocoa.rb is a good idea, I would prefer rubycocoa.rb instead.
This is a temporarily compatible layer, designed to help people port their RubyCocoa app to MacRuby. The purpose is not to provide a layer on which people can rely on eternally. So having developers explicitly require rubycocoa.rb is better IMHO (and anyway, in the most cases, this will be an Xcode app that has to be modified to link against MacRuby.)
Also, I don't think it's a good idea to duplicate the whole osx/*.rb environment then.
I don't completely agree with you on these points. As for now I do not intend to completely port my apps to MacRuby, also because I simply don't have the time. But I would like to be able to develop further on MacRuby while still being able to use RC if it's necessary. So this is I guess the main difference in our points of view.
But to get back to the real issue at hand, sure I understand it's better to remind developers that using the layer is not the optimal way of using MacRuby.
I'll remove osx/cocoa.rb and add it to Rucola.
After thinking about this, I changed my mind, and agree with yours. Let's stick to osx/cocoa. Also, I filed http://ruby.macosforge.org/trac/ticket/89 regarding pure C RubyCocoa APIs that also need to be emulated (I will take care of this). Laurent