tag:blogger.com,1999:blog-29194345.post8252825373221683539..comments2009-01-26T23:09:23.164-08:00Chrishttp://www.blogger.com/profile/14204551800123292694noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-29194345.post-54891616656190722752008-09-06T16:19:00.000-07:002008-09-06T16:19:00.000-07:00@elliottcable You want to call the registration function from awakeFromNib in your main controller/UI code.Chrishttp://www.blogger.com/profile/14204551800123292694noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-1153453480804443362008-09-05T22:57:00.000-07:002008-09-05T22:57:00.000-07:00I'm curious as to *where* I can put that code in my RubyCocoa app. I created a new non-Document 'Core Data' RubyCocoa application, and while the Info.plist section did, in fact, cause OS X to launch my app when I typed 'myapp:test' in Safari's address bar... it didn't *do* anything. As far as I could tell, `getUrl_withReplyEvent` never got called (I placed `system "say '#{url}'"` in there to test exactly that).<BR/><BR/>I put all the code into rb_main.rb, and it seemed to have no effect - here's the exact code I needed:<BR/>http://gist.github.com/9058<BR/><BR/>Is the `registerMyApp` method called automatically at some point? Or do I need to call that from somewhere in the initialization myself? I tried placing a call to `registerMyApp` from the `rb_main_init` method, but that didn't help.<BR/><BR/>Oh, one small note - you need `OSX::NSAppleEventManager` instead of just `NSAppleEventManager` in your example code.elliottcablehttp://elliottcable.name/noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-2044852709919712492008-08-15T15:54:00.000-07:002008-08-15T15:54:00.000-07:00I haven't tried MacRuby yet. The last time I checked, it wasn't far enough along. I haven't had occasion to work in RubyCocoa in the last couple months, so it's been a while. I was happy to see MacRuby being done, just adds more to the mix. If you try it, let me know what you think.Chrishttp://www.blogger.com/profile/14204551800123292694noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-86165253470825544732008-08-11T12:50:00.000-07:002008-08-11T12:50:00.000-07:00Cool beans. I might try to build something in Ruby now [a MondoMouse competitor] instead of in straight Objective C. This could be fun. Also have you tried macruby? I assume it's about the same? Thanks.<BR/>-Rmormonhttp://famousmormons.net/noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-41104969295558208042008-03-20T09:51:00.000-07:002008-03-20T09:51:00.000-07:00Andy, I put the <A HREF="http://codeintensity.blogspot.com/2008/03/creating-sparkle-appcast-via-rake-tasks.html" REL="nofollow">Rake tasks</A> up, hope it helps.Chrishttp://www.blogger.com/profile/14204551800123292694noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-83846692180707303062008-03-20T08:24:00.000-07:002008-03-20T08:24:00.000-07:00Andy, glad it helped - I wish I'd had that. You'd think this would be some standard stuff they'd have in the docs, but maybe they don't expect this as mainstream, or they're still ramping up the docs. <BR/><BR/>As for Sparkle, good idea, I'll post my rake tasks in another blog post, will work on that today. There is actually NO code for Sparkle! Their implementation is great, you literally drop the thing in with Interface Builder, hook it to your menu, and off you go (check the Sparkle site for instructions).Chrishttp://www.blogger.com/profile/14204551800123292694noreply@blogger.comtag:blogger.com,1999:blog-29194345.post-7258363483059408232008-03-20T07:03:00.000-07:002008-03-20T07:03:00.000-07:00Thanks,<BR/><BR/>The events code really saved me a lot of time.<BR/><BR/>Any chance of a sneaky peak at your sparkle code and the rake file you talk of?Andy Kenthttp://www.blogger.com/profile/14305231590511592487noreply@blogger.com