From: Axel R. <axe...@ro...> - 2014-11-02 09:09:58
|
I also have some old projects in RubyCocoa and deploying them with libraries was always troublesome. I was reluctant to convert the heavy string manipulations into Objective-C. Have a look at swift: Apple's new language. It might well be that they killed off MacRuby because they knew swift was coming. It is not ruby, but highly inspired, shall we say? https://developer.apple.com/swift/ Cheers, Axel Roest Sent from the road, so beware of bumps in the text! > On 2 nov. 2014, at 06:17, Dave Howell <gro...@gr...> wrote: > > I sat down to update an old program, resigned to having to rewrite it for MacRuby, only to discover that “the replacement for RubyCocoa” is, in fact, dead. > > I’m awfully glad RubyCocoa is still here; there’s no way I”m ever going to waste time with Objective-C, but I admit I’m wondering if anybody else is using RubyCocoa, either, since I can’t seem to find anybody having mentioned the fact that XCode 5.1’s Interface Builder seems to have lost the ability to find the outlets. My app’s controller > > class AppController << OSX::NSWindowController > blah blah blah > end > > is no longer comprehensible or visible to Interface Builder. Is this being fixed, or is there some bit that didn’t get installed, or am I just really lucky and it’s only my install that’s broken? > ------------------------------------------------------------------------------ > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |