Comments on: Creating our very first Mac application with Ruby, how exciting!

By: Anthony

Anthony — Fri, 19 Aug 2011 07:01:41 +0000

Really nice tutorial. One thing I’ve noticed though, is that it won’t work on xcode 4.1, 4.2 and Lion, because of an issue with xcode. Bug and a possible workaround are described here: http://www.macruby.org/trac/ticket/1322, but it seems that the problem is in xcode, not macruby, so I guess we’re gonna have to wait until the next release and hope it gets resolved.

By: What I’m doing 07/12/2011 « Shingonoide's Blog

What I’m doing 07/12/2011 « Shingonoide's Blog — Tue, 12 Jul 2011 10:07:58 +0000

[...] Creating our very first Mac application with Ruby, how exciting! – Phusion Corporate Blog [...]

By: remco

remco — Tue, 10 May 2011 06:47:56 +0000

Thank you for posting this,
Just want you to let you know this post can be used for xcode 4 as wel, everything works about the same,

one question, why does your fist app say 42 instead of hello world

By: links for 2011-01-17 « Bloggitation

links for 2011-01-17 « Bloggitation — Tue, 18 Jan 2011 06:04:15 +0000

[...] Creating our very first Mac application with Ruby, how exciting! (tags: mac osx ruby cocoa programming) [...]

By: MacRuby, ou comment développer des applications Mac avec Ruby! | Neoweb Mag : Dev

Fri, 22 Oct 2010 10:28:03 +0000

[...] anglais).Le MacRuby: The Definitive Guide de Matt Aimonetti (en anglais).Le tutoriel « Creating our very first Mac application with Ruby » (en anglais).Le screencast d’Alex Vollmer et Geoffrey Grosenbach : [...]

By: Emerson Vinicius

Emerson Vinicius — Thu, 21 Oct 2010 12:30:50 +0000

Nice! Post

The detail was amazing.

By: MacRuby + Mac App Store == Low Hanging Fruit for Rubyists

MacRuby + Mac App Store == Low Hanging Fruit for Rubyists — Thu, 21 Oct 2010 11:11:27 +0000

[...] Creating our very first Mac application with Ruby is a great (and recent) step-by-step [...]

By: Sowmya Gopinth

Sowmya Gopinth — Wed, 11 Aug 2010 23:06:01 +0000

hi,
first of all your tutorial was great. It helped me get started with macruby developement. Iam now building a MacRuby and stuck with packaging the app for distribution.

i get the following err when i try to install the build

Process: macRubyTestApplication [885]
Path: /Users/satish/Downloads/macRubyTestApplication.1.app/Contents/MacOS/macRubyTestApplication
Identifier: com.yourcompany.macRubyTestApplication
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [119]

Interval Since Last Report: 2631 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 0 sec
Per-App Crashes Since Last Report: 2

Date/Time: 2010-08-11 18:25:40.304 -0400
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: DFB7FE92-E92A-47C2-B386-F0146BDF3384

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0×0000000000000002, 0×0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/MacRuby.framework/Versions/0.6/usr/lib/libmacruby.dylib
Referenced from: /Users/satish/Downloads/macRubyTestApplication.1.app/Contents/MacOS/macRubyTestApplication
Reason: no suitable image found. Did find:
/Users/satish/Downloads/macRubyTestApplication.1.app/Contents/MacOS/../Frameworks/MacRuby.framework/Versions/0.6/usr/lib/libmacruby.dylib: unknown required load command 0×80000022
/Users/satish/Downloads/macRubyTestApplication.1.app/Contents/MacOS/../Frameworks/MacRuby.framework/Versions/0.6/usr/lib/libmacruby.dylib: unknown required load command 0×80000022

Can you please tell me what steps should i follow to build the app. how to embed the macruby framework in the build.

Thanks

Sowmya

By: Objective-C for Ruby developers, un not-so-petit interlude (1/2) – Phusion Corporate Blog

Wed, 24 Mar 2010 21:52:05 +0000

[...] les amis! Welcome back to to this second installment of our tour de MacRuby! In the previous article, we went over the basics of XCode and Interface Builder. With this preliminary knowledge, we were [...]

By: Ninh Bui

Ninh Bui — Wed, 24 Mar 2010 14:50:31 +0000

@Björn:
Well, with MacRuby you can write native OSX Cocoa-based applications because it’s capable of compiling it to native code and using only one runtime, being the same objective C runtime native OSX apps utilize. A bridge however, incorporates two runtimes as mentioned before, where in the case of Py-Objc for example, a python runtime interacts with the objective-C runtime to for example, interface with the Cocoa API. A similar scenario is applicable to RubyCocoa. With MacRuby however, you don’t have these separate runtimes anymore to deal with: just one, being the Objective-C runtime which allows you to mix and match Ruby and Objective-C code, something we’ll touch on in the follow up to this article. I hope this has clarified that a bit up: don’t confuse RubyCocoa for MacRuby, the former is a bridge, the latter allows for a single runtime native solution.

As for your claim about the Python interpreter compiling the script before it runs, unfortunately, we haven’t had enough experience with the Python internals to verify whether or not this is the case. However, if true, it would mean that the Python interpreter would “just-in-time” compile it. By the time of this writing MacRuby does this as well, but I believe heuristics may be on its way to only JIT when its responsible too (e.g. depending on caller frequency etc…) as JIT comes at the cost of memory (e.g. storing the native code in RAM) and performance (e.g. translating the code to native). As far as I’m aware of, there were some add-ons that would allow Python to JIT compile (Psyco for example), but by default Python does not: it probably only compiles it down to VM opcodes (bytecode), similar as Ruby 1.9 does this. This however, is not native. It simply speeds up the interpretation process by not having to traverse and interpret the abstract syntax tree (AST), but just a series of opcodes instead. MacRuby does not do this, instead, it just compiles it directly to native code for execution.