Re: [MacRuby-devel] MacRuby on Mavericks (or go to RubyMotion?)

2013-11-24 Thread Joshua Ballanco 
Hey Rob,

Glad to hear that your experience has been so good thus far! I can vouch for 
the guys at HipByte, and I’m sure they will be more than willing to help you 
(or anyone) out along the way as you make the transition (and hit the 
inevitable road-bumps). As for IB support and the lack of Xcode, I think there 
are more people out that that feel as you do that there is still value in a 
graphical UI design tool. I don’t think there’s anything imminently ready for 
release, but it might be good to keep your eyes on the folks over at JetBrains 
as well as what the HipByte team is up to.

Cheers,

Josh  


On Friday, November 22, 2013 at 22:39, rob ista wrote:

 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-requ...@lists.macosforge.org 
 (mailto:macruby-devel-requ...@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.i...@me.com (mailto:rob.i...@me.com)
  To: macruby-devel@lists.macosforge.org 
  (mailto:macruby-devel@lists.macosforge.org)
  Subject: Re: [MacRuby-devel] MacRuby on Mavericks
  Message-ID: e00cb811-65f3-4b93-a0fc-4c2158d9b...@me.com 
  (mailto:e00cb811-65f3-4b93-a0fc-4c2158d9b...@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 to happy with my MacRuby apps :) ? 
  May be moving

Re: [MacRuby-devel] MacRuby on Mavericks (or go to RubyMotion?)

2013-11-22 Thread rob ista 
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-requ...@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.i...@me.com
 To: macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: e00cb811-65f3-4b93-a0fc-4c2158d9b...@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 to 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.au...@pobox.com
 To: MacRuby development discussions.
   macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: 8579b5dd-9d34-41dd-9cef-2e41532f0...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-13 Thread Joshua Ballanco 
On Sunday, November 10, 2013 at 8:16 AM, Robert Carl Rice wrote:
 
 On Nov 7, 2013, at 9:07 AM, Joshua Ballanco jball...@gmail.com 
 (mailto:jball...@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.

Yes. In fact, the only real benefit that rb-nibtool brings is that it would run 
automatically (i.e. without the need for user interaction) to update the list 
of IBOutlets and IBActions every time you fired up interface builder. A while 
back some of us on the team played with the idea of a tool to automatically 
generate header files as you've done manually, but the problem is that you'd 
still need to explicitly run it every time your ruby file changed (or use 
something fun like kicker to run it for you on file change notifications).
 
 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.

In fact, you should be able to get away with just the .h file and keep using 
the attr_* methods in your Ruby code. So long as nothing #imports the .h file, 
it has no impact on the build process, but it's presence in your Xcode project 
should be enough for Xcode's parser to generate the appropriate hooks for 
Interface Builder.

Cheers,

Josh


___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-10 Thread rob ista 
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-requ...@lists.macosforge.org wrote:

 Send MacRuby-devel mailing list submissions to
   macruby-devel@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-requ...@lists.macosforge.org
 
 You can reach the person managing the list at
   macruby-devel-ow...@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.au...@pobox.com
 To: MacRuby development discussions.
   macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: 8e18a9e4-8eb5-4c0c-8627-7d4c758dc...@pobox.com
 Content-Type: text/plain; charset=us-ascii
 
 
 On Nov 7, 2013, at 9:07 AM, Joshua Ballanco jball...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-10 Thread Robert Carl Rice 
Hi Rob,

One other comment on your example.

I see that you have subclassed NSWindowController in your AppDelegate. That is 
good for the window to be restorable. However, NSWindowController will define 
it's own window property as an IBOutlet so you don't want to override that with 
your own window IBOutlet.

Bob Rice


On Nov 10, 2013, at 4:19 AM, rob ista rob.i...@me.com wrote:

 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
 

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-09 Thread Robert Carl Rice 

On Nov 7, 2013, at 9:07 AM, Joshua Ballanco jball...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread david kramf 
 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 markv...@gmail.com
 To: MacRuby development discussions.
 macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: eb5cfea0-0397-442c-b0c9-a3fa3228b...@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.au...@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@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel
 -- next part --
 An HTML attachment was scrubbed...
 URL: 
 http://lists.macosforge.org/pipermail/macruby-devel/attachments/20131105/a6503aac/attachment-0001.html
 
 --
 
 Message: 3
 Date: Tue, 5 Nov 2013 13:42:32 -0500
 From: Robert Carl Rice rice.au...@pobox.com
 To: MacRuby development discussions.
 macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: e19ac16e-8e6f-4006-b443-39f1cdf1b...@pobox.com
 Content-Type: text/plain; charset=us-ascii
 
 Hi Mark,
 
 Thanks, I took a quick look at IB gem documentation.
 
 It looks like a possibility for me although it also looks like it could be 
 difficult to maintain. You have to run rake ib:open every time you make a 
 change in your ruby files.
 
 Ruby programmers will have a natural aversion to anything cryptic and 
 unmaintainable as, for example, Unix shell script. Any solution I see seems 
 like a throwback in sophistication. It took time for me to become familiar 
 with XCODE so I'm not anxious to give up on it even with frequent crashes.
 
 PS. It seems to me that Xcode crashes because it gets to have too many 
 files open in the editor and it will restore those open files when 
 relaunched and continue to crash. But, doing a normal quit and relaunch 
 will close files. Is there a shortcut to close all editor files?
 
 Bob Rice
 
 
 On Nov 5, 2013, at 3:46 AM, Mark Villacampa markv...@gmail.com wrote:
 
 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.au...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Perry E. Metzger 
On Thu, 07 Nov 2013 11:20:13 +0200 david kramf dakr@gmail.com
wrote:
 I have a project that written in MacRuby but I can split the code
 to logic  in Ruby and the UI which I can translate to Objective-C .
 So My problem is how to run a pure Ruby from my app. I was thinking
 of opening an AppleScript terminal and running IRB there . Has
 anyone tried it? Do you have a better easier idea ? Is it doable ??
 Thnks, David Kramf

First, it is unnecessary to use a terminal to fork a subprocess
running ruby, and clearly unnecessary to use applescript for any of
this. You can simply use the normal Unix fork/exec to set up a
subprocess, which you can then communicate with via pipes, unix
domain sockets, etc. Second, irb is the interactive ruby shell, you
need not use that.

You can also simply link together the ruby interpreter and your
application -- the ruby foreign function interface makes this
reasonably straightforward.

Still, I think the main import of all such discussions is that there
remains a large constituency for developing applications in Ruby for
the Mac, but that MacRuby is clearly not the wave of the future for
this.

-- 
Perry E. Metzgerpe...@piermont.com
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Joshua Ballanco 
-devel
  or, via email, send a message with subject or body 'help' to
  macruby-devel-requ...@lists.macosforge.org 
  (mailto:macruby-devel-requ...@lists.macosforge.org)
   
  You can reach the person managing the list at
  macruby-devel-ow...@lists.macosforge.org 
  (mailto:macruby-devel-ow...@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.au...@pobox.com (mailto:rice.au...@pobox.com)
  To: MacRuby development discussions.
  macruby-devel@lists.macosforge.org 
  (mailto:macruby-devel@lists.macosforge.org)
  Subject: [MacRuby-devel] MacRuby on Mavericks
  Message-ID: 9ea268fc-55d6-4f3e-8372-d2b831d58...@pobox.com 
  (mailto:9ea268fc-55d6-4f3e-8372-d2b831d58...@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 markv...@gmail.com (mailto:markv...@gmail.com)
  To: MacRuby development discussions.
  macruby-devel@lists.macosforge.org 
  (mailto:macruby-devel@lists.macosforge.org)
  Subject: Re: [MacRuby-devel] MacRuby on Mavericks
  Message-ID: eb5cfea0-0397-442c-b0c9-a3fa3228b...@gmail.com 
  (mailto:eb5cfea0-0397-442c-b0c9-a3fa3228b...@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.au...@pobox.com 
   (mailto:rice.au...@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@lists.macosforge.org

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Robert Carl Rice 
 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 markv...@gmail.com
 To: MacRuby development discussions.
macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: eb5cfea0-0397-442c-b0c9-a3fa3228b...@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.au...@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@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel
 -- next part --
 An HTML attachment was scrubbed...
 URL: 
 http://lists.macosforge.org/pipermail/macruby-devel/attachments/20131105/a6503aac/attachment-0001.html
 
 --
 
 Message: 3
 Date: Tue, 5 Nov 2013 13:42:32 -0500
 From: Robert Carl Rice rice.au...@pobox.com
 To: MacRuby development discussions.
macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: e19ac16e-8e6f-4006-b443-39f1cdf1b...@pobox.com
 Content-Type: text/plain; charset=us-ascii
 
 Hi Mark,
 
 Thanks, I took a quick look at IB gem documentation.
 
 It looks like a possibility for me although it also looks like it could be 
 difficult to maintain. You have to run rake ib:open every time you make a 
 change in your ruby files.
 
 Ruby programmers will have a natural aversion to anything cryptic and 
 unmaintainable as, for example, Unix shell script. Any solution I see 
 seems like a throwback in sophistication. It took time for me to become 
 familiar with XCODE so I'm not anxious to give up on it even with frequent 
 crashes.
 
 PS. It seems to me that Xcode crashes because it gets to have too many 
 files open in the editor and it will restore those open files when 
 relaunched and continue to crash. But, doing a normal quit and relaunch 
 will close files. Is there a shortcut to close all editor files?
 
 Bob Rice
 
 
 On Nov 5, 2013, at 3:46 AM, Mark Villacampa markv...@gmail.com wrote:
 
 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.au...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Perry E. Metzger 
On Thu, 07 Nov 2013 09:52:44 -0500 Robert Carl Rice
rice.au...@pobox.com wrote:
 Hi David,
 
 The implementation of Grand Central Dispatch in MacRuby works great
 and I converted all of calls to NSTimer to GCD. It probably has
 enough functionality to avoid any Kludgy solution, e.g., calling
 Unix fork directly or AppleScript.

That's not what he's asking, at least I don't think. He wants to use
straight Objective C for his UI and to use ordinary Ruby for his
application logic.

Perry

 On Nov 7, 2013, at 4:20 AM, david kramf dakr@gmail.com wrote:
 
  Hi Guys,
  
  I have a project that written in MacRuby but I can split the code
  to logic  in Ruby and the UI which I can translate to
  Objective-C . So My problem is how to run a pure Ruby from my
  app. I was thinking of opening an AppleScript terminal and
  running IRB there . Has anyone tried it? Do you have a better
  easier idea ? Is it doable ?? Thnks, David Kramf
  

-- 
Perry E. Metzgerpe...@piermont.com
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Matthias Neeracher 
Thanks for your detailed explanation.

On Nov 7, 2013, at 15:07, Joshua Ballanco jball...@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

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-07 Thread Perry E. Metzger 
On Thu, 07 Nov 2013 20:09:49 +0100 Matthias Neeracher
neerac...@apple.com wrote:
 Thanks for your detailed explanation.
 
 On Nov 7, 2013, at 15:07, Joshua Ballanco jball...@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.

And when Mavericks goes away and it gets removed instead of just
being deprecated? A longer term solution is needed if one actually
wants to keep the thing running...

Pery
-- 
Perry E. Metzgerpe...@piermont.com
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-06 Thread rob ista 
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 to 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-requ...@lists.macosforge.org wrote:

 Send MacRuby-devel mailing list submissions to
   macruby-devel@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-requ...@lists.macosforge.org
 
 You can reach the person managing the list at
   macruby-devel-ow...@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.au...@pobox.com
 To: MacRuby development discussions.
   macruby-devel@lists.macosforge.org
 Subject: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: 9ea268fc-55d6-4f3e-8372-d2b831d58...@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 markv...@gmail.com
 To: MacRuby development discussions.
   macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: eb5cfea0-0397-442c-b0c9-a3fa3228b...@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.au...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-06 Thread Robert Carl Rice 
 
 
 
 --
 
 Message: 2
 Date: Tue, 5 Nov 2013 09:46:14 +0100
 From: Mark Villacampa markv...@gmail.com
 To: MacRuby development discussions.
  macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: eb5cfea0-0397-442c-b0c9-a3fa3228b...@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.au...@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@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel
 -- next part --
 An HTML attachment was scrubbed...
 URL: 
 http://lists.macosforge.org/pipermail/macruby-devel/attachments/20131105/a6503aac/attachment-0001.html
 
 --
 
 Message: 3
 Date: Tue, 5 Nov 2013 13:42:32 -0500
 From: Robert Carl Rice rice.au...@pobox.com
 To: MacRuby development discussions.
  macruby-devel@lists.macosforge.org
 Subject: Re: [MacRuby-devel] MacRuby on Mavericks
 Message-ID: e19ac16e-8e6f-4006-b443-39f1cdf1b...@pobox.com
 Content-Type: text/plain; charset=us-ascii
 
 Hi Mark,
 
 Thanks, I took a quick look at IB gem documentation.
 
 It looks like a possibility for me although it also looks like it could be 
 difficult to maintain. You have to run rake ib:open every time you make a 
 change in your ruby files.
 
 Ruby programmers will have a natural aversion to anything cryptic and 
 unmaintainable as, for example, Unix shell script. Any solution I see seems 
 like a throwback in sophistication. It took time for me to become familiar 
 with XCODE so I'm not anxious to give up on it even with frequent crashes.
 
 PS. It seems to me that Xcode crashes because it gets to have too many files 
 open in the editor and it will restore those open files when relaunched and 
 continue to crash. But, doing a normal quit and relaunch will close files. 
 Is there a shortcut to close all editor files?
 
 Bob Rice
 
 
 On Nov 5, 2013, at 3:46 AM, Mark Villacampa markv...@gmail.com wrote:
 
 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.au...@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

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-06 Thread Kevin Walzer 

On 11/6/13, 9:00 PM, Robert Carl Rice wrote:

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.


Can you be more specific about how they are not compatible?

--
Kevin Walzer
Code by Kevin/Mobile Code by Kevin
http://www.codebykevin.com
http://www.wtmobilesoftware.com
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-06 Thread Robert Carl Rice 
Hi Kevin,

No, except that when I tried to upgrade to Mavericks I got undefined class 
object errors from the MacRuby framework as per Rob Ista's message. Hopefully 
it's just a load order problem.

Bob Rice


On Nov 6, 2013, at 9:37 PM, Kevin Walzer k...@codebykevin.com wrote:

 On 11/6/13, 9:00 PM, Robert Carl Rice wrote:
 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.
 
 Can you be more specific about how they are not compatible?
 
 -- 
 Kevin Walzer
 Code by Kevin/Mobile Code by Kevin
 http://www.codebykevin.com
 http://www.wtmobilesoftware.com
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-05 Thread Mark Villacampa 
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.au...@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@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-05 Thread Robert Carl Rice 
Hi Mark,

Thanks, I took a quick look at IB gem documentation.

It looks like a possibility for me although it also looks like it could be 
difficult to maintain. You have to run rake ib:open every time you make a 
change in your ruby files.

Ruby programmers will have a natural aversion to anything cryptic and 
unmaintainable as, for example, Unix shell script. Any solution I see seems 
like a throwback in sophistication. It took time for me to become familiar with 
XCODE so I'm not anxious to give up on it even with frequent crashes.

PS. It seems to me that Xcode crashes because it gets to have too many files 
open in the editor and it will restore those open files when relaunched and 
continue to crash. But, doing a normal quit and relaunch will close files. Is 
there a shortcut to close all editor files?

Bob Rice


On Nov 5, 2013, at 3:46 AM, Mark Villacampa markv...@gmail.com wrote:

 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.au...@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@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macruby-devel

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel

Re: [MacRuby-devel] MacRuby on Mavericks

2013-11-05 Thread Stephen Horne 

On 5 Nov 2013, at 18:42, Robert Carl Rice wrote:


Thanks, I took a quick look at IB gem documentation.
It looks like a possibility for me although it also looks like it 
could be difficult to maintain. You have to run rake ib:open every 
time you make a change in your ruby files.


I suppose you could have something like the kicker gem running in the 
background watching for changes to .rb files and running the rake 
command when it sees one.


Ruby programmers will have a natural aversion to anything cryptic and 
unmaintainable as, for example, Unix shell script. Any solution I see 
seems like a throwback in sophistication. It took time for me to 
become familiar with XCODE so I'm not anxious to give up on it even 
with frequent crashes.
PS. It seems to me that Xcode crashes because it gets to have too many 
files open in the editor and it will restore those open files when 
relaunched and continue to crash. But, doing a normal quit and 
relaunch will close files. Is there a shortcut to close all editor 
files?


Not one that I know of. Xcode seems to ignore the system-wide settings 
for this (as it does with many other settings). I believe that Xcode is 
applescriptable enough to write something that loops through the open 
tabs and shuts them before quitting however.


Failing that, I know that you can reset the window state inside an Xcode 
project by deleting the UserInterfaceState.xcuserstate file found here:


xcode_project.xcodeproj/project.xcworkspace/xcuserdata/username.xcuserdatad/UserInterfaceState.xcuserstate


Bob Rice



--
Stephen Horne
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macruby-devel