Re: [Rubycocoa-talk] [ANN]RubyCocoa 1.1.0

[Gregory C. <gr...@in...>]

I’m also incredibly grateful that RubyCocoa is still here. I’ve been using it since 2008. I had one app written in MacRuby to try it out, but when garbage collection was deprecated in Mavericks it stopped working, so I rewrote it in RubyCocoa.

The automatic outlets disappeared awhile ago for me. Simple solution is to create an Objective C header file with matching ib_outlets and ib_actions . For example:

#import <Cocoa/Cocoa.h>

@interface AppController : NSObject
{
	IBOutlet NSWindow *mainWindow;
	IBOutlet NSButton *openFileButton;
	IBOutlet NSTextField *fileName;
	IBOutlet NSWindow *progressWindow;
	IBOutlet NSView *progressView;
	IBOutlet NSProgressIndicator *progressIndicator;
	IBOutlet NSTextField *progressMessage;
}
- (IBAction)chooseFile:(id)sender;
- (IBAction)saveFile:(id)sender;
@end

> On Nov 1, 2014, at 10:17 PM, 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