[Rubycocoa-talk] Hooray for RubyCocoa (was: Re: [ANN]RubyCocoa 1.1.0)

[Dave H. <gro...@gr...>]

I should have changed the subject in the first place. Oops. 

> 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 . 

Awesome. I’d never have figured that out. 

What I actually did, though, was use TimeMachine to recover a version of MainMenu.nib from before the InterfaceBuilder in XCode 5 touched it. Then I opened my project in XCode 3.x under 10.6, or at least opened the .nib file with that version of Interface Builder. My new outlets were right where I expected them to be. I made the new connections, saved it, then opened the project back under 10.10 and XCode 5 for compilation. 

As I’d expected, “new” XCode will still happily use old-school .nib files. I suspect I can …. {checks version numbers} oh, really??? Interesting! So “interface builder” is now built into XCode, but there’s still a copy of Interface Builder 3.2.6 on my OSX 10.10 machine, which is the same version on my OSX 10.6 machine. 

If I open the .nib file in Interface Builder rather than XCode, it looks like the outlets and whatnot are still available for connecting. How very useful . . . . I just have to make sure not to accidentally open and save the .nib in XCode, or it will no longer be possible to use Interface Builder to edit it. 

Also, thanks to those of you who pointed me at Swift. However, most of my programming isn’t really for OS X. Most of it’s database<->web work running on an Ubuntu server, and I don’t think Swift is going to be a terribly workable replacement for that any time soon, so I’d really rather just stick with one language for now, especially since, as a hobbyist, I spend a not-inconsiderable amount of time just re-learning what I used to know when I sit down to program (as in, oh, every couple of months).