November 2013 - MacRuby-devel - lists.macosforge.org

Re: [MacRuby-devel] MacRuby on Mavericks (or go to RubyMotion?)
by rob ista 24 Nov '13

24 Nov '13

Hi all, I went to RubyMotion about 10 days ago and I must admit it made me happy (after some struggles :) … the migration is actually not that difficult: just install the IB gem, replace the attr-accessors to the use of the gem, dump the rb files in the app-folder and the rest in the resources-folder, RAKE, and there you go !!! :))) … … well, actually it caused some pain. The variable type handling is a little more strict so obviously my sloppy work caused troubles after all. As an example, obviously the GC in MacRuby was not perfect so a reference to a variable that should have been already erased worked in MacRuby but will not work in RubyMotion. type changes are more tough but you should do that anyway. :) . Well, a good opportunity to clean up your code :))) … Also Mavericks is not that stable yet and is also more strict with calls. So sometimes you just have to take another route. Further more the error reporting is not always that clear … Cleaning up that code without knowing what was wrong at first kept me from sleeping a while because very very often you just get crash-reports with a lot of %$^#%. Sometimes I just had to put a “puts “break here !!!"” line by line to find out where the crash came from. Working like this sometimes looked like the 70’s were you would get an inch thick memory dump after a programming error :) … … The lack of Xcode integration is a matter of taste. I think its a step backwards because we are developing for IOS or OSX anyway so why abandon the Apple stuff ? but fortunately the IB gem at least makes NIB’s accessible so no hard coding of windows (unless you want to). It will take me another week or so to get an app ready for the store again but I am already happy I can use it myself again … it’s all a bit back to basic again but hey, we’re explorers anyway living on the edge of software engineering of today :) … … finally i’d like to say that Laurent and his team are really on top of it and don’t seem to sleep to deliver proper progress and support. Thanks guys !!! … well, for me MacRuby is dead, long live RubyMotion :))) cheers, Rob On 07 Nov 2013, at 03:00, macruby-devel-request(a)lists.macosforge.org wrote: > > Today's Topics: > > 1. Re: MacRuby on Mavericks (rob ista) > 2. Re: MacRuby on Mavericks (Robert Carl Rice) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 06 Nov 2013 22:27:42 +0100 > From: rob ista <rob.ista(a)me.com> > To: macruby-devel(a)lists.macosforge.org > Subject: Re: [MacRuby-devel] MacRuby on Mavericks > Message-ID: <E00CB811-65F3-4B93-A0FC-4C2158D9B1F2(a)me.com> > Content-Type: text/plain; charset=windows-1252 > > Hi All, > > indeed the GC is still there on Mavericks and needs to be ?required? in Xcode while disabling ARC to avoid a conflict (thanks Steve). So far so good. I guess I had too many probe at the same time :). The malfunctioning again of the IB in Xcode5 with the outlets can be solved with the earlier published workaround of an accompanying ObjC Class.h file next to the MacRuby Class.rb file. It?s a bit additional work to create and maintain but we?re talking about a few minutes here so that should not be a problem unless you have to maintain many many classes with outlets. Obviously the rb-nibtool is not called or not working anymore even when properly installed. > > What is a bigger problem is that not all objects seem to be created at run-time resulting in no-method errors (e.g. with gems) and sometimes not connected outlets in delegate classes or unresolved IB-action methods. Pretty weird. The same sources compile and run fine on SL-L-ML . For me it?s difficult to trace why and where this happens so hopefully an expert can shine a light on this. Very simple apps run fine, bigger ones with just more classes and stuff crash. > > I am moving back to ML and keep may be a little "play machine? on a separate disk with Mavericks. I am tooooo happy with my MacRuby apps :) ? May be moving to RubyMotion after all. I will test it at least soon. Laurent deserves the support and its not that much money :). > > cheers, Rob > > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 6 Nov 2013 21:00:02 -0500 > From: Robert Carl Rice <rice.audio(a)pobox.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] MacRuby on Mavericks > Message-ID: <8579B5DD-9D34-41DD-9CEF-2E41532F09CE(a)pobox.com> > Content-Type: text/plain; charset=windows-1252 > > Hi Rob, > > Thanks for looking into this. > > The iTunes Store has notified me that my current binaries will be removed from the store for not being compatible with the current OS release. Recoding for either RubyMotion or Objective-C will be a big job and I'm not looking forward to it. > > PS; the new Xcode renews the warning that Xcode 5 is scheduled to be the last Xcode version to support GC, but I don't see anything that ties version 6 to a scheduled OS update. > > Bob Rice > > > On Nov 6, 2013, at 4:27 PM, rob ista <rob.ista(a)me.com> wrote: > >> Hi All, >> >> indeed the GC is still there on Mavericks and needs to be ?required? in Xcode while disabling ARC to avoid a conflict (thanks Steve). So far so good. I guess I had too many probe at the same time :). The malfunctioning again of the IB in Xcode5 with the outlets can be solved with the earlier published workaround of an accompanying ObjC Class.h file next to the MacRuby Class.rb file. It?s a bit additional work to create and maintain but we?re talking about a few minutes here so that should not be a problem unless you have to maintain many many classes with outlets. Obviously the rb-nibtool is not called or not working anymore even when properly installed. >> >> What is a bigger problem is that not all objects seem to be created at run-time resulting in no-method errors (e.g. with gems) and sometimes not connected outlets in delegate classes or unresolved IB-action methods. Pretty weird. The same sources compile and run fine on SL-L-ML . For me it?s difficult to trace why and where this happens so hopefully an expert can shine a light on this. Very simple apps run fine, bigger ones with just more classes and stuff crash. >> >> I am moving back to ML and keep may be a little "play machine? on a separate disk with Mavericks. I am tooooo happy with my MacRuby apps :) ? May be moving to RubyMotion after all. I will test it at least soon. Laurent deserves the support and its not that much money :). >> >> cheers, Rob >> >> >> >> On 05 Nov 2013, at 19:55, macruby-devel-request(a)lists.macosforge.org wrote: >> >>> Send MacRuby-devel mailing list submissions to >>> macruby-devel(a)lists.macosforge.org >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> https://lists.macosforge.org/mailman/listinfo/macruby-devel >>> or, via email, send a message with subject or body 'help' to >>> macruby-devel-request(a)lists.macosforge.org >>> >>> You can reach the person managing the list at >>> macruby-devel-owner(a)lists.macosforge.org >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of MacRuby-devel digest..." >>> >>> >>> Today's Topics: >>> >>> 1. MacRuby on Mavericks (Robert Carl Rice) >>> 2. Re: MacRuby on Mavericks (Mark Villacampa) >>> 3. Re: MacRuby on Mavericks (Robert Carl Rice) >>> 4. Re: MacRuby on Mavericks (Stephen Horne) >>> >>>

2 1

Re: [MacRuby-devel] MacRuby on Mavericks
by rob ista 14 Nov '13

14 Nov '13

Hi All, indeed the GC is still there on Mavericks and needs to be ‘required’ in Xcode while disabling ARC to avoid a conflict (thanks Steve). So far so good. I guess I had too many probe at the same time :). The malfunctioning again of the IB in Xcode5 with the outlets can be solved with the earlier published workaround of an accompanying ObjC Class.h file next to the MacRuby Class.rb file. It’s a bit additional work to create and maintain but we’re talking about a few minutes here so that should not be a problem unless you have to maintain many many classes with outlets. Obviously the rb-nibtool is not called or not working anymore even when properly installed. What is a bigger problem is that not all objects seem to be created at run-time resulting in no-method errors (e.g. with gems) and sometimes not connected outlets in delegate classes or unresolved IB-action methods. Pretty weird. The same sources compile and run fine on SL-L-ML . For me it’s difficult to trace why and where this happens so hopefully an expert can shine a light on this. Very simple apps run fine, bigger ones with just more classes and stuff crash. I am moving back to ML and keep may be a little "play machine” on a separate disk with Mavericks. I am tooooo happy with my MacRuby apps :) … May be moving to RubyMotion after all. I will test it at least soon. Laurent deserves the support and its not that much money :). cheers, Rob On 05 Nov 2013, at 19:55, macruby-devel-request(a)lists.macosforge.org wrote: > Send MacRuby-devel mailing list submissions to > macruby-devel(a)lists.macosforge.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.macosforge.org/mailman/listinfo/macruby-devel > or, via email, send a message with subject or body 'help' to > macruby-devel-request(a)lists.macosforge.org > > You can reach the person managing the list at > macruby-devel-owner(a)lists.macosforge.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. MacRuby on Mavericks (Robert Carl Rice) > 2. Re: MacRuby on Mavericks (Mark Villacampa) > 3. Re: MacRuby on Mavericks (Robert Carl Rice) > 4. Re: MacRuby on Mavericks (Stephen Horne) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 4 Nov 2013 22:02:58 -0500 > From: Robert Carl Rice <rice.audio(a)pobox.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: [MacRuby-devel] MacRuby on Mavericks > Message-ID: <9EA268FC-55D6-4F3E-8372-D2B831D588B0(a)pobox.com> > Content-Type: text/plain; charset=us-ascii > > Hi, > > Nice that I sparked some discussion. > > One of the reasons that I continued to write MacRuby script even though Xcode was giving me the warning that GC was deprecated is that I suspect that was a mostly a political move to appease the egos of the IOS and ARC guys and also to encourage programmers to write more efficient code. Even if Apple is determined not to support GC on the mobile devices, there is probable no really good technical reason to remove the capability for desktop apps. So I would have been surprised if Apple had removed GC in Mavericks and I still would be surprised if Apple does that anytime soon, if they do that at all. > > If would be a mistake, because the relative simplicity of script language programming is what makes it possible for a lonesome programmer such as myself to develop and maintain a couple of relatively large applications. The problem with RubyMotion is that it does an end-run around Xcode and since my apps do lots of initialization using NIB files it may be as much work for me to convert to RubyMotion as it will be to rewrite in objective-C. > > I don't have any inside information on Apple's thinking, but I suspect that may be worth the effort to upgrade MacRuby for Mavericks. I'll let you know when I find out if the App Store will still still support MacRuby apps. > > Bob Rice > > > > ------------------------------ > > Message: 2 > Date: Tue, 5 Nov 2013 09:46:14 +0100 > From: Mark Villacampa <markvjal(a)gmail.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] MacRuby on Mavericks > Message-ID: <EB5CFEA0-0397-442C-B0C9-A3FA3228BCCE(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hey Bob, > > Have you seen the IB gem? It let's you use nibs with Rubymotion with minimal changes in your MacRuby code. > > https://github.com/yury/ib > > Sent from my iPhone > >> On 05/11/2013, at 04:02, Robert Carl Rice <rice.audio(a)pobox.com> wrote: >> >> Hi, >> >> Nice that I sparked some discussion. >> >> One of the reasons that I continued to write MacRuby script even though Xcode was giving me the warning that GC was deprecated is that I suspect that was a mostly a political move to appease the egos of the IOS and ARC guys and also to encourage programmers to write more efficient code. Even if Apple is determined not to support GC on the mobile devices, there is probable no really good technical reason to remove the capability for desktop apps. So I would have been surprised if Apple had removed GC in Mavericks and I still would be surprised if Apple does that anytime soon, if they do that at all. >> >> If would be a mistake, because the relative simplicity of script language programming is what makes it possible for a lonesome programmer such as myself to develop and maintain a couple of relatively large applications. The problem with RubyMotion is that it does an end-run around Xcode and since my apps do lots of initialization using NIB files it may be as much work for me to convert to RubyMotion as it will be to rewrite in objective-C. >> >> I don't have any inside information on Apple's thinking, but I suspect that may be worth the effort to upgrade MacRuby for Mavericks. I'll let you know when I find out if the App Store will still still support MacRuby apps. >> >> Bob Rice >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/macruby-devel >

6 11

Re: [MacRuby-devel] MacRuby on Mavericks
by rob ista 10 Nov '13

10 Nov '13

Isn’t it enough to have a Class.h file as company of the Ruby.rb file like: // AppDelegate.h #import <Foundation/Foundation.h> @interface AppDelegate : NSWindowController { IBOutlet NSWindow *window; IBOutlet NSButton *homeButton; . . . etc etc } - (IBAction)loadStore:(id)sender; - (IBAction)sortContacts:(id)sender; . . . etc etc @end At least the IB is triggered by this but I admit i still don't have a big app running on Mavericks :) cheers, Rob On 10 Nov 2013, at 07:16, macruby-devel-request(a)lists.macosforge.org wrote: > Send MacRuby-devel mailing list submissions to > macruby-devel(a)lists.macosforge.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.macosforge.org/mailman/listinfo/macruby-devel > or, via email, send a message with subject or body 'help' to > macruby-devel-request(a)lists.macosforge.org > > You can reach the person managing the list at > macruby-devel-owner(a)lists.macosforge.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. Re: MacRuby on Mavericks (Robert Carl Rice) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 10 Nov 2013 01:16:12 -0500 > From: Robert Carl Rice <rice.audio(a)pobox.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] MacRuby on Mavericks > Message-ID: <8E18A9E4-8EB5-4C0C-8627-7D4C758DC6E2(a)pobox.com> > Content-Type: text/plain; charset="us-ascii" > > > On Nov 7, 2013, at 9:07 AM, Joshua Ballanco <jballanc(a)gmail.com> wrote: > >> * MacRuby integration with Xcode relies on rb-nibtool, but the Xcode team has repeatedly signaled (not so subtly) that they are not interested in keeping this shim working. > > I assume that rb-nibtool scans rb files to identify possible IBOutlet and IBAction targets. If this is it's only function then I would not miss it if it goes away. I have discovered that it is easy to define IBOutlet and IBAction targets in Objective-C files without recoding any ruby code into Objective-C. The results are much better because the linkage and error messages are very fast while the scanning of ruby files gets very slow on a large project. > > To avoid adding a lot of files, I created a single Objective-C .h and .m file for each of my nib files, including the main, giving it a corresponding name. > > // MainWindow.h > // RiceCNC > // > // Created by Robert Rice on 11/9/13. > // Copyright (c) 2013 Robert Rice. All rights reserved. > // > > #import <Foundation/Foundation.h> > > @interface AppDelegate : NSObject > > @property (weak) IBOutlet id template_menu; > @property (weak) IBOutlet id example_menu; > > - (IBAction)makeNewMachine:(id)sender; > - (IBAction)makeNewEngine:(id)sender; > > @end > > // MainWindow.m > // RiceCNC > // > // Created by Robert Rice on 11/9/13. > // Copyright (c) 2013 Robert Rice. All rights reserved. > // > > #import "MainWindow.h" > > @implementation AppDelegate > > @synthesize template_menu; > @synthesize example_menu; > > - (IBAction)makeNewMachine:(id)sender {}; > - (IBAction)makeNewEngine:(id)sender {}; > > @end > > The IBActions are easy. I simply define empty methods for my actions. MacRuby will replace the empty methods with the ruby methods. > > For each IBOutlet, I define a C property, remove the attr_writer or attr_accessor from my ruby class, then reference the property from my ruby class using the dot syntax. > > For this example, I changed @template_menu to self.template_menu and @example_menu to self.example_menu: > > # AppDelegate.rb > # MacCNC > # > # Created by Robert Rice on 3/10/12. > # Copyright 2012 Rice Audio. All rights reserved. > > class AppDelegate > # attr_writer :template_menu, :example_menu > > def init > if super > # ErrorLog.instance.debug( "AppDelegate init" ) > end > @pdf_window_controller = nil > @mail_bridge_window_controller = nil > > self > end > > def awakeFromNib > # ErrorLog.instance.debug( "AppDelegate awakeFromNib" ) > bundle = NSBundle.mainBundle > > engines = bundle.pathsForResourcesOfType( "engine", inDirectory:"Templates" ) > engines.each do | path | > title = path.split( '/' ).last.split( '.' ).first > item = self.template_menu.addItemWithTitle( title, action:"open_engine_template:", keyEquivalent:"" ) > item.setTarget( self ) > end > > examples = bundle.pathsForResourcesOfType( "cnc", inDirectory:"Examples" ) > examples.each do | path | > title = path.split( '/' ).last.split( '.' ).first > item = self.example_menu.addItemWithTitle( title, action:"open_document_template:", keyEquivalent:"" ) > item.setTarget( self ) > end > end > > def makeNewMachine( sender ) > makeNewDocument( "Machine" ) > end > > def makeNewEngine( sender ) > makeNewDocument( "Engine" ) > end > > def makeNewDocument( type ) > ErrorLog.instance.warn( "makeNewDocument #{ type }" ) > > nserror = Pointer.new( :object ) > controller = NSDocumentController.sharedDocumentController > document = controller.makeUntitledDocumentOfType( type, error:nserror ) > if document > controller.addDocument( document ) > document.makeWindowControllers > document.showWindows > > else > ErrorLog.instance.error( "Error creating new #{ type } Document" ) > end > > document > end > > def open_engine_template( sender ) > open_file( NSBundle.mainBundle.pathForResource( sender.title, ofType:"engine", inDirectory:"Templates" ) ) > end > > def open_machine_template( sender ) > open_file( NSBundle.mainBundle.pathForResource( sender.title, ofType:"machine", inDirectory:"Templates" ) ) > end > > def open_document_template( sender ) > open_file( NSBundle.mainBundle.pathForResource( sender.title, ofType:"cnc", inDirectory:"Examples" ) ) > end > > def open_file( path ) > url = NSURL.fileURLWithPath( path ) > nserror = Pointer.new( :object ) > NSDocumentController.sharedDocumentController.openDocumentWithContentsOfURL( url, > display:true, error:nserror ) > end > > end > > > >

2 2

Re: [MacRuby-devel] MacRuby on Mavericks
by Matthias Neeracher 07 Nov '13

07 Nov '13

Thanks for your detailed explanation. On Nov 7, 2013, at 15:07, Joshua Ballanco <jballanc(a)gmail.com> wrote: > I had planed on writing a longer message to the list but, having just started a new gig, time is severely lacking. Also, it seems it'll be at least 2-3 weeks (thank Apple store ship times) before I get a chance to test anything on Mavericks. Here's what I can tell you so far: > > * Replacing the GC is semi-problematic But that also should not be a problem for Mavericks, because clearly GC works just fine in Mavericks. > All that said, if getting MacRuby running on Mavericks doesn't take more than 2-3 weekends of spare time, I'll see what I can do. As it stands, the port to a more recent version of llvm is already mostly done on a branch... Once that is done, I’d be happy to try pitching in to fix the method definition problem that is plaguing MacRuby on Mavericks. Matthias

2 1

Standard Ruby for desktop apps?
by Kevin Walzer 07 Nov '13

07 Nov '13

With MacRuby seemingly abandoned, is there any constituency for using standard Ruby for Mac desktop deployment? I was very interested in trying to use Ruby with Tk, but was stymied by the lack of deployment API's. Tk is old-school, but it has the virtue of actually working with standard Ruby when nearly every other Ruby UI toolkit and framework does not (wxRuby, etc.) Is there any way to abstract any of the MacRuby/Ruby-Cocoa packaging tools (such as standalonify) into a general app bundling package? --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com

3 3

MacRuby on Mavericks
by Robert Carl Rice 05 Nov '13

05 Nov '13

Hi, Nice that I sparked some discussion. One of the reasons that I continued to write MacRuby script even though Xcode was giving me the warning that GC was deprecated is that I suspect that was a mostly a political move to appease the egos of the IOS and ARC guys and also to encourage programmers to write more efficient code. Even if Apple is determined not to support GC on the mobile devices, there is probable no really good technical reason to remove the capability for desktop apps. So I would have been surprised if Apple had removed GC in Mavericks and I still would be surprised if Apple does that anytime soon, if they do that at all. If would be a mistake, because the relative simplicity of script language programming is what makes it possible for a lonesome programmer such as myself to develop and maintain a couple of relatively large applications. The problem with RubyMotion is that it does an end-run around Xcode and since my apps do lots of initialization using NIB files it may be as much work for me to convert to RubyMotion as it will be to rewrite in objective-C. I don't have any inside information on Apple's thinking, but I suspect that may be worth the effort to upgrade MacRuby for Mavericks. I'll let you know when I find out if the App Store will still still support MacRuby apps. Bob Rice

3 3

Re: [MacRuby-devel] Mavericks and Macruby
by rob ista 04 Nov '13

04 Nov '13

Steve? Where is it then? Is it de-activated or sth? When I try to run a simple macruby app in xcode i get an error message that the GC is depreciated. Rob The garbage collector is deprecated but it's still there in Mavericks. Steve

2 1

Re: [MacRuby-devel] Mavericks and Macruby
by Matthias Neeracher 03 Nov '13

03 Nov '13

On Nov 3, 2013, at 3:44, macruby-devel-request(a)lists.macosforge.org wrote: > From: rob ista <rob.ista(a)me.com> > > Something seems to be broken since the upgrade to Mavericks. Macgems don?t want to load anymore: > > Robs-iMac:~ rob$ macgem list > /usr/local/bin/macgem:9:in `<main>': undefined method `summary_indent=' for class `OptionParser' (NameError) > > This is just an example. A ?require macgems? followed by e.g. ?require uri? results in similar errors. > > Anyone any clue? I investigated this a few months ago. The immediate cause of the breakage would not be terribly hard to fix—there was a change to the caching behavior of the Objective C runtime, so MacRuby would have to be changed a bit. The bigger problem I found is that MacRuby relies on a version of llvm that by now is quite dated and no longer builds with current clang, and upgrading to a newer llvm appears to be non-trivial (Although this is not really my area of expertise). Matthias

1 0

Mavericks and Macruby
by rob ista 03 Nov '13

03 Nov '13

Something seems to be broken since the upgrade to Mavericks. Macgems don’t want to load anymore: Robs-iMac:~ rob$ macgem list /usr/local/bin/macgem:9:in `<main>': undefined method `summary_indent=' for class `OptionParser' (NameError) This is just an example. A ‘require macgems’ followed by e.g. ‘require uri’ results in similar errors. Anyone any clue?

7 8

Re: [MacRuby-devel] Mavericks and Macruby
by rob ista 03 Nov '13

03 Nov '13

Oooops, yes Stephen, of course the GC is depreciated. Obviously my brain didn’t want to accept that so i just forgot :))) … well, so far MacRuby and the current AppStore apps. I pulled them out. First i thought that the small ones without gems still worked, but they’ll crash sooner or later. It’s quite amazing how in fact none of the higher level languages really survived in 30 years time. We’re all still stuck with C (and it’s derivates like C++. Jave, C#, Obj-C, …) May be Laurent and his team can write a migration guide to RubyMotion? I’m sure that attracts customers :P. And I know he doesn’t like Xcode but it will help people move to RM :))) Rob > Date: Sun, 03 Nov 2013 11:20:16 +0000 > From: "Stephen Horne" <fatste(a)gmail.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] Mavericks and Macruby > Message-ID: <B136BC33-F984-4C6A-A317-EEA7D1D0D751(a)gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 3 Nov 2013, at 0:32, Joshua Ballanco wrote: > >> I haven't had time to update to Mavericks yet, so I couldn't tell you >> for sure, but the "summary_indent=" error looks like it may be a >> consequence of the upgraded 2.0 version of Ruby on the system. IIRC, >> there should still be a copy of the 1.8 Ruby version (under >> /System/Library I think?). If you change the #! line in "macgem" to >> point specifically to Ruby 1.8, things may start working again? > > I'm confused - I thought that there was no chance of using MacRuby on > Mavericks because it depends on the garbage collector that no longer > exists. Is that incorrect? > -- > Stephen Horne > >

1 0