Noob question: Interface builder not picking up MacRuby definitions
Hi, Please forgive me if this is the wrong list for my questions. I'm just getting started with MacRuby, and running through several examples (like the one here http://www.macruby.org/documentation/tutorial.html) I've noticed that Interface Builder doesn't always pick up stuff defined by MacRuby classes, and some of the examples don't seem to work for me. In that tutorial I got to this line:
"You will then see that IB knows about your class, and especially the outlet and action defined earlier."
Aside from the fact that the tutorial seems to have been written for an earlier version of Xcode, the Identity Inspector in Interface Builder does pick up the class but it doesn't pick up the actions or outlets. I try tying them up myself in the panel in the Library window but after build and run it still doesn't work properly. In the MacRuby book on O'Reilly's site http://macruby.labs.oreilly.com/ch04.html#_bindings I couldn't get it to even pick up the class in the Identity Inspector until I had it derive from an NS class. Coding the GUI directly with the AppKit framework does work, however (http://macruby.labs.oreilly.com/ch01.html#_code_example), so I know it *could* work. I'm on Xcode 3.2.3 and MacRuby 0.6 and OSX 10.6.4. I'm new to Xcode too, which I reinstalled to make sure it wasn't that. I gritted my teeth and did some Obj-C examples and they worked fine. I tried converting some Obj-C examples into MacRuby and they didn't work. Sometimes they'd build and run but events wouldn't work as expected, sometimes GDB would give the "app exited with error 1" error message. Is there something I've missed or need to install, or is it that MacRuby is still too new to work all the time? Any help much appreciated, as this project looks very, very helpful. Regards, Iain
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating. I'm a MacRuby noob myself, so sorry if this doesn't apply in the MacRuby context. /Felix 2010/9/15 Iain Barnett <iainspeed@gmail.com>:
Hi,
Please forgive me if this is the wrong list for my questions. I'm just getting started with MacRuby, and running through several examples (like the one here http://www.macruby.org/documentation/tutorial.html) I've noticed that Interface Builder doesn't always pick up stuff defined by MacRuby classes, and some of the examples don't seem to work for me.
In that tutorial I got to this line:
"You will then see that IB knows about your class, and especially the outlet and action defined earlier."
Aside from the fact that the tutorial seems to have been written for an earlier version of Xcode, the Identity Inspector in Interface Builder does pick up the class but it doesn't pick up the actions or outlets. I try tying them up myself in the panel in the Library window but after build and run it still doesn't work properly.
In the MacRuby book on O'Reilly's site http://macruby.labs.oreilly.com/ch04.html#_bindings I couldn't get it to even pick up the class in the Identity Inspector until I had it derive from an NS class.
Coding the GUI directly with the AppKit framework does work, however (http://macruby.labs.oreilly.com/ch01.html#_code_example), so I know it *could* work. I'm on Xcode 3.2.3 and MacRuby 0.6 and OSX 10.6.4. I'm new to Xcode too, which I reinstalled to make sure it wasn't that. I gritted my teeth and did some Obj-C examples and they worked fine. I tried converting some Obj-C examples into MacRuby and they didn't work. Sometimes they'd build and run but events wouldn't work as expected, sometimes GDB would give the "app exited with error 1" error message.
Is there something I've missed or need to install, or is it that MacRuby is still too new to work all the time? Any help much appreciated, as this project looks very, very helpful.
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file. This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it. Or maybe I am as unlucky as my lottery winnings suggest? :( Regards, Iain
Have you recently updated your Xcode installation? I find that every time I install a new version of Xcode, I have to re-install MacRuby to get the IB integration to work again. -Gabriel On Wed, Sep 15, 2010 at 3:50 AM, Iain Barnett <iainspeed@gmail.com> wrote:
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file.
This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it.
Or maybe I am as unlucky as my lottery winnings suggest? :(
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On 15 Sep 2010, at 17:15, Gabriel Gilder wrote:
Have you recently updated your Xcode installation? I find that every time I install a new version of Xcode, I have to re-install MacRuby to get the IB integration to work again.
-Gabriel
Woo hoo! That worked. Thanks, I did reinstall Xcode, basically because this wasn't working from the start. I'd also reinstalled MacRuby previously but I can't remember in which order I did it now, but it's worked out ok in the end :) Thanks for the help, I doubt I'd have tried that again if you hadn't mentioned it happened to you too. Iain
Hi Iain: As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it. I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers. Hope this helps. Bob Rice On Sep 15, 2010, at 6:50 AM, Iain Barnett wrote:
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file.
This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it.
Or maybe I am as unlucky as my lottery winnings suggest? :(
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Bob, Hopefully you've opened a bug on the IB performance you've observed. I'm sure the team would be very interested in a perf problem that makes IB that unusable. Matt On Sep 15, 2010, at 9:35 AM, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
On Sep 15, 2010, at 6:50 AM, Iain Barnett wrote:
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file.
This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it.
Or maybe I am as unlucky as my lottery winnings suggest? :(
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Matt: No, I didn't. I assumed it would be a known issue. Any idea when Xcode 4 will available for general use? Thanks, Bob Rice On Sep 15, 2010, at 12:39 PM, Matt Massicotte wrote:
Bob,
Hopefully you've opened a bug on the IB performance you've observed. I'm sure the team would be very interested in a perf problem that makes IB that unusable.
Matt
On Sep 15, 2010, at 9:35 AM, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
On Sep 15, 2010, at 6:50 AM, Iain Barnett wrote:
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file.
This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it.
Or maybe I am as unlucky as my lottery winnings suggest? :(
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Even if it is a known issue, which is very well may be, developer feedback is still extremely important. Your bug could shed additional light on the problem, could show that external developers are hitting it, or could even be the first report anyone has seen. I know it's a pain, but external bug reports are very helpful. Matt On Sep 15, 2010, at 9:48 AM, Robert Rice wrote:
Hi Matt:
No, I didn't. I assumed it would be a known issue. Any idea when Xcode 4 will available for general use?
Thanks, Bob Rice
On Sep 15, 2010, at 12:39 PM, Matt Massicotte wrote:
Bob,
Hopefully you've opened a bug on the IB performance you've observed. I'm sure the team would be very interested in a perf problem that makes IB that unusable.
Matt
On Sep 15, 2010, at 9:35 AM, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
On Sep 15, 2010, at 6:50 AM, Iain Barnett wrote:
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
This might not be it, but IB is in generall pretty bad at picking up changes in code. Try Reload All Class Files from the File menu. When you're coding Objective-C you sometimes even have to do "Read All Class Files..." and manually point IB to the right header file. IB is great in general, but this can be pretty frustrating."
Thanks for the reply. I tried reloading the files and no change. I also tried dragging the file into the IB window but get the message "Parsed 1 source file but no classes were found or changed. I get this message even if I do change the file.
This is repeatable and only happens with MacRuby, (I just tested it with a brand new project) so I don't think it's (solely) down to this kind of flakiness or I'd expect to work once in the n times I've tried it.
Or maybe I am as unlucky as my lottery winnings suggest? :(
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On 15 Sep 2010, at 17:35, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
Thanks Bob, I'll keep that in mind. I did try to get my hands on the Xcode 4 beta to see if it fixed the issue but the link was dead. It definitely makes sense to combine the windows. Regards, Iain
The link is not dead, but I had to try a bunch of times, over the course of a day, before I got the download to start. /F 2010/9/15 Iain Barnett <iainspeed@gmail.com>:
On 15 Sep 2010, at 17:35, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
Thanks Bob, I'll keep that in mind. I did try to get my hands on the Xcode 4 beta to see if it fixed the issue but the link was dead. It definitely makes sense to combine the windows.
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Felix: Does the new Xcode 4 have any issues with MacRuby or can we start using it as soon as it's available? Bob Rice On Sep 15, 2010, at 1:02 PM, Felix Holmgren wrote:
The link is not dead, but I had to try a bunch of times, over the course of a day, before I got the download to start.
/F
2010/9/15 Iain Barnett <iainspeed@gmail.com>:
On 15 Sep 2010, at 17:35, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
Thanks Bob, I'll keep that in mind. I did try to get my hands on the Xcode 4 beta to see if it fixed the issue but the link was dead. It definitely makes sense to combine the windows.
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
The current available version of Xcode 4 does not have MacRuby support (at least not in the Interface Builder part). This means IB in Xcode 4 is not able to find outlets or actions. -- Thibault Martin-Lagardette On Sep 15, 2010, at 10:09, Robert Rice wrote:
Hi Felix:
Does the new Xcode 4 have any issues with MacRuby or can we start using it as soon as it's available?
Bob Rice
On Sep 15, 2010, at 1:02 PM, Felix Holmgren wrote:
The link is not dead, but I had to try a bunch of times, over the course of a day, before I got the download to start.
/F
2010/9/15 Iain Barnett <iainspeed@gmail.com>:
On 15 Sep 2010, at 17:35, Robert Rice wrote:
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class information. Because of that I tend to avoid using IB to link outlets. Instead I tag my subfields and search for then in my initialization scripts using view.viewWithTag and for my new MacRuby classes I paste in the superclass information rather than waiting for IB to find it.
I think this slowness to update is a main reason for integrating IB with Xcode 4. Unfortunately Xcode 4 is still only available to paid developers.
Hope this helps.
Bob Rice
Thanks Bob, I'll keep that in mind. I did try to get my hands on the Xcode 4 beta to see if it fixed the issue but the link was dead. It definitely makes sense to combine the windows.
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Just out of curiosity: does this mean that the IB team are working independently to support MacRuby intergration? /F 2010/9/15 Thibault Martin-Lagardette <thibault.ml@gmail.com>:
The current available version of Xcode 4 does not have MacRuby support (at least not in the Interface Builder part). This means IB in Xcode 4 is not able to find outlets or actions.
-- Thibault Martin-Lagardette
On Sep 15, 2010, at 10:09, Robert Rice wrote:
Hi Felix:
Does the new Xcode 4 have any issues with MacRuby or can we start using it as soon as it's available?
Not knowing the release schedule for Xcode 4, is lack of support for MacRuby in IB in Xcode 4 a blocking issue for the 0.7 release? On Wed, Sep 15, 2010 at 12:09 PM, Felix Holmgren <felix.holmgren@gmail.com> wrote:
Just out of curiosity: does this mean that the IB team are working independently to support MacRuby intergration?
/F
2010/9/15 Thibault Martin-Lagardette <thibault.ml@gmail.com>:
The current available version of Xcode 4 does not have MacRuby support (at least not in the Interface Builder part). This means IB in Xcode 4 is not able to find outlets or actions.
-- Thibault Martin-Lagardette
On Sep 15, 2010, at 10:09, Robert Rice wrote:
Hi Felix:
Does the new Xcode 4 have any issues with MacRuby or can we start using it as soon as it's available?
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Iain, This is really strange. Could you tell us what version of Mac OS X you run and what version of Xcode and MacRuby you installed? Also, do you happen to run a 32-bit only Intel machine? If you installed a new version of Xcode on top of a previous MacRuby installation, you may want to re-install MacRuby. If IB isn't picking up the metadata you may see messages in your console. Please paste any relevant information here. IB is using the /Developer/usr/bin/rb_nibtool command-line tool to retrieve metadata. You can call it by yourself on the terminal, passing a path to your Ruby file, and see what happens. If you get a property-list describing the relevant classes/outlets/actions then it means the problem is elsewhere. Laurent On Sep 15, 2010, at 2:33 AM, Iain Barnett wrote:
Hi,
Please forgive me if this is the wrong list for my questions. I'm just getting started with MacRuby, and running through several examples (like the one here http://www.macruby.org/documentation/tutorial.html) I've noticed that Interface Builder doesn't always pick up stuff defined by MacRuby classes, and some of the examples don't seem to work for me.
In that tutorial I got to this line:
"You will then see that IB knows about your class, and especially the outlet and action defined earlier."
Aside from the fact that the tutorial seems to have been written for an earlier version of Xcode, the Identity Inspector in Interface Builder does pick up the class but it doesn't pick up the actions or outlets. I try tying them up myself in the panel in the Library window but after build and run it still doesn't work properly.
In the MacRuby book on O'Reilly's site http://macruby.labs.oreilly.com/ch04.html#_bindings I couldn't get it to even pick up the class in the Identity Inspector until I had it derive from an NS class.
Coding the GUI directly with the AppKit framework does work, however (http://macruby.labs.oreilly.com/ch01.html#_code_example), so I know it *could* work. I'm on Xcode 3.2.3 and MacRuby 0.6 and OSX 10.6.4. I'm new to Xcode too, which I reinstalled to make sure it wasn't that. I gritted my teeth and did some Obj-C examples and they worked fine. I tried converting some Obj-C examples into MacRuby and they didn't work. Sometimes they'd build and run but events wouldn't work as expected, sometimes GDB would give the "app exited with error 1" error message.
Is there something I've missed or need to install, or is it that MacRuby is still too new to work all the time? Any help much appreciated, as this project looks very, very helpful.
Regards, Iain _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sorry for the slow response, I've been occupied elsewhere. On 16 Sep 2010, at 06:02, Laurent Sansonetti wrote:
If you installed a new version of Xcode on top of a previous MacRuby installation, you may want to re-install MacRuby.
It's working now I've reinstalled both Xcode and then MacRuby. It wasn't working before that, but I can't be sure I hadn't upgraded Xcode in the time between the original MacRuby install and this problem.
This is really strange. Could you tell us what version of Mac OS X you run and what version of Xcode and MacRuby you installed? Also, do you happen to run a 32-bit only Intel machine?
It's a Macbook Pro with a Intel Core 2 Duo, which I understand is 64-bit but System Profiler says that 64 bit kernel and extensions are a "no". OSX 10.6.4 is on there, and MacRuby 0.6 from the installer not the source, and Xcode is version 3.2.3 (1688). Interface Builder is version 3.2.3 (788).
If IB isn't picking up the metadata you may see messages in your console. Please paste any relevant information here.
Haven't seen anything in there. So little in fact that I'm a little bit perturbed, things never run that well! :)
IB is using the /Developer/usr/bin/rb_nibtool command-line tool to retrieve metadata. You can call it by yourself on the terminal, passing a path to your Ruby file, and see what happens. If you get a property-list describing the relevant classes/outlets/actions then it means the problem is elsewhere.
If I see this happening again I'll try this and see what I can find out. I really appreciate all the help. Regards, Iain
Hi Iain, On Sep 19, 2010, at 10:58 AM, Iain Barnett wrote:
Sorry for the slow response, I've been occupied elsewhere.
On 16 Sep 2010, at 06:02, Laurent Sansonetti wrote:
If you installed a new version of Xcode on top of a previous MacRuby installation, you may want to re-install MacRuby.
It's working now I've reinstalled both Xcode and then MacRuby. It wasn't working before that, but I can't be sure I hadn't upgraded Xcode in the time between the original MacRuby install and this problem.
I see. The Ruby IB support that Xcode ships with does not support MacRuby, so MacRuby has to overwrite it during its installation. It means that if you install or upgrade Xcode after an existing MacRuby installation, the IB support will be reverted and MacRuby has to be re-installed. Glad to hear it's now working for you :) Laurent
participants (8)
-
Andy Stechishin
-
Felix Holmgren
-
Gabriel Gilder
-
Iain Barnett
-
Laurent Sansonetti
-
Matt Massicotte
-
Robert Rice
-
Thibault Martin-Lagardette