February 2011 - MacRuby-devel - lists.macosforge.org

stopping to build for i386
by Laurent Sansonetti 26 Feb '11

26 Feb '11

Hi, As of r5239 in trunk, the default build process will no longer build for both i386 and x86_64, but just x86_64. This is an attempt at accelerating the build process and reducing the framework objects size. We are however not removing any i386-related code from the project, and one will still be able to build a 32-bit version of MacRuby by passing archs=i386 to rake. We will also consider fixing i386 bugs. But we want to start discouraging people to target i386 hardware for MacRuby apps, for several reasons (codebase not well tested, runtime / exception handling differences, floating point precision loss, etc.). The i386-related code could eventually be removed from MacRuby after 0.10. This is not an irrevocable decision, though. If people complain we will revert the change. But I want to give it a try. Laurent

2 2

iokit again
by Joel Reymont 26 Feb '11

26 Feb '11

I'm chomping at the bit to have IOKit support in MacRuby. Can you tell me what needs to be done for IOKit support [1]? I may be able to do the work and submit a patch. Thanks in advance, Joel [1] http://www.macruby.org/trac/ticket/1126 -------------------------------------------------------------------------- - mac osx device driver ninja, kernel extensions and user-land usb drivers ---------------------+------------+--------------------------------------- http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont ---------------------+------------+---------------------------------------

2 1

[ANN] MacRuby 0.9
by Laurent Sansonetti 25 Feb '11

25 Feb '11

Hi, After about 2 months of development since the last release, MacRuby 0.9 is now available. Get it here while it's still hot! MacRuby is an implementation of Ruby 1.9 directly on top of Mac OS X core technologies such as the Objective-C runtime and garbage collector, the LLVM compiler infrastructure and the Foundation and ICU frameworks. It is the goal of MacRuby to enable the creation of full-fledged Mac OS X applications which do not sacrifice performance in order to enjoy the benefits of using Ruby. You can learn more about MacRuby, and download a binary installer, from the website: http://macruby.org Or about this release more specifically, on our blog: http://www.macruby.org/blog/2011/02/24/macruby09.html Enjoy, Laurent

2 1

Re: [MacRuby-devel] loop audio file seamlessly (Zachary Kaplan)
by Zachary Kaplan 24 Feb '11

24 Feb '11

hello all, i received a suggestion from another member to check out the PlayFile example in the audio toolbox examples. while this was very helpful in putting me on the right track for basic low level audio manipulation, there are some additional related issues i've encountered in trying to port over the example to macruby. most notably, i don't seem to have some of the most important methods available such as AudioFileOpenURL. perhaps (most likely) i am just doing something wrong. i have bridge support 2. also if anyone has any macruby audio examples, i'd love to see what others have done. could anyone else provide some more insight? thanks in advance -zak

3 2

#init, or #initialize
by Rob Gleeson 24 Feb '11

24 Feb '11

Hi It seems on MacRuby 0.8 that a subclass of NSWindowController has #init called, but #initialize is not called. It seems really odd to have two different initialize methods, and particularly when one of them breaks away from what is convention in Ruby. Is this intended? Thanks Rob

2 2

Re: [MacRuby-devel] MacRuby-devel Digest, Vol 36, Issue 42
by Zachary Kaplan 24 Feb '11

24 Feb '11

Shaun August, I have previously come across the same suggestion you mentioned: using QTKit's QTMovie class for playing/looping audio. After implementing the QTKit approach which you can see here: https://github.com/razic/virus/blob/master/loop.rb the pause between each loop iteration was either the same or worse than a basic NSSound object with loops = true. Neither the NSSound or the QTMovie are sufficient for seamless looping. However, the Apple PlayFile example which I built/compiled in Xcode DOES loop perfectly seamless. How come I can't access a lot of the methods you see in the PlayFile example, even after loading the necessary frameworks? (I have BridgeSupport 2) I hope I'm simply doing something wrong. Would really appreciate anyone who can provide any sort of insight into converting PlayFile to macruby. PlayFile can be found here: http://developer.apple.com/library/mac/#samplecode/PlayFile/Introduction/In… Thanks in advance, Zak On Wed, Feb 23, 2011 at 3:18 PM, <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 > http://lists.macosforge.org/mailman/listinfo.cgi/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: loop audio file seamlessly (Zachary Kaplan) (Shaun August) > 2. NoMethodError (ib_outlets) (Rob Gleeson) > 3. Re: NoMethodError (ib_outlets) (Robert Payne) > 4. Re: NoMethodError (ib_outlets) (Laurent Sansonetti) > 5. Re: 0.9 update (Laurent Sansonetti) > 6. Re: NoMethodError (ib_outlets) (Rob Gleeson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 23 Feb 2011 10:13:57 -0800 > From: Shaun August <saugust(a)me.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Cc: "macruby-devel(a)lists.macosforge.org" > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] loop audio file seamlessly (Zachary > Kaplan) > Message-ID: <78467B80-E4AB-407D-80BF-97CD162F262A(a)me.com> > Content-Type: text/plain; CHARSET=US-ASCII > > Hi Zak, > > Try looking at the QTMovie. It is much more reliable and handles audio well. If you need a sample I can post something tonight. > > > Thank you, > > > On 2011-02-22, at 10:27 PM, Zachary Kaplan <razic(a)viralkitty.com> wrote: > >> hello all, >> >> i received a suggestion from another member to check out the PlayFile >> example in the audio toolbox examples. >> >> while this was very helpful in putting me on the right track for basic >> low level audio manipulation, there are some additional related issues >> i've encountered in trying to port over the example to macruby. >> >> most notably, i don't seem to have some of the most important methods >> available such as AudioFileOpenURL. >> >> perhaps (most likely) i am just doing something wrong. i have bridge support 2. >> >> also if anyone has any macruby audio examples, i'd love to see what >> others have done. >> >> could anyone else provide some more insight? >> >> thanks in advance >> -zak >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > ------------------------------ > > Message: 2 > Date: Wed, 23 Feb 2011 21:57:35 +0000 > From: Rob Gleeson <rob(a)flowof.info> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: [MacRuby-devel] NoMethodError (ib_outlets) > Message-ID: <64937216-981F-4469-BB80-C76C98E78EF8(a)flowof.info> > Content-Type: text/plain; charset=us-ascii > > Hi > > I'm giving my first MacRuby application a shot, and I'm sort of blind to be honest :) > I've added a NSWindowController, attached it to my window, saved the classes in Interface Builder, but when I build and run my application, I get a > NoMethodError for 'ib_outlets'. > > My controller inherits from NSResponder. > > The stranger thing is, I guess, when I remove any code referencing ib_outlets, the same error is raised again. NoMethodError. > > Any advice? What class defines ib_outlets? Am I doing it completely wrong? > Thanks. > > -- > Rob > > > > > > > > ------------------------------ > > Message: 3 > Date: Thu, 24 Feb 2011 11:08:59 +1300 > From: Robert Payne <robertpayne(a)me.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] NoMethodError (ib_outlets) > Message-ID: <F8170B8F-E4E2-4849-BFCB-C431C1378152(a)me.com> > Content-Type: text/plain; CHARSET=US-ASCII > > Hey Rob, > > Could you by chance upload the source to github or somewhere? It'd be a lot easier to help seeing the whole picture. > > -Robert > > On Feb 24, 2011, at 10:57 AM, Rob Gleeson wrote: > >> Hi >> >> I'm giving my first MacRuby application a shot, and I'm sort of blind to be honest :) >> I've added a NSWindowController, attached it to my window, saved the classes in Interface Builder, but when I build and run my application, I get a >> NoMethodError for 'ib_outlets'. >> >> My controller inherits from NSResponder. >> >> The stranger thing is, I guess, when I remove any code referencing ib_outlets, the same error is raised again. NoMethodError. >> >> Any advice? What class defines ib_outlets? Am I doing it completely wrong? >> Thanks. >> >> -- >> Rob >> >> >> >> >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > ------------------------------ > > Message: 4 > Date: Wed, 23 Feb 2011 14:13:51 -0800 > From: Laurent Sansonetti <lsansonetti(a)apple.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] NoMethodError (ib_outlets) > Message-ID: <E5824773-93C4-4EDE-8FBC-64DA6CD22683(a)apple.com> > Content-Type: text/plain; charset="us-ascii" > > Hi Rob, > > ib_outlets is an old RubyCocoa craft that is not supported in MacRuby since a long time. You can define IB outlets using the attr_writer or attr_accessor methods. You can define IB actions by defining methods accepting a single argument, named 'sender'. > > There are lots of documentation about this on the net. Here is a pointer to a nice tutorial that you might be interested to follow. > > http://blog.phusion.nl/2010/03/12/creating-our-very-first-mac-application-w… > > Laurent > > On Feb 23, 2011, at 1:57 PM, Rob Gleeson wrote: > >> Hi >> >> I'm giving my first MacRuby application a shot, and I'm sort of blind to be honest :) >> I've added a NSWindowController, attached it to my window, saved the classes in Interface Builder, but when I build and run my application, I get a >> NoMethodError for 'ib_outlets'. >> >> My controller inherits from NSResponder. >> >> The stranger thing is, I guess, when I remove any code referencing ib_outlets, the same error is raised again. NoMethodError. >> >> Any advice? What class defines ib_outlets? Am I doing it completely wrong? >> Thanks. >> >> -- >> Rob >> >> >> >> >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > >

1 0

NoMethodError (ib_outlets)
by Rob Gleeson 23 Feb '11

23 Feb '11

Hi I'm giving my first MacRuby application a shot, and I'm sort of blind to be honest :) I've added a NSWindowController, attached it to my window, saved the classes in Interface Builder, but when I build and run my application, I get a NoMethodError for 'ib_outlets'. My controller inherits from NSResponder. The stranger thing is, I guess, when I remove any code referencing ib_outlets, the same error is raised again. NoMethodError. Any advice? What class defines ib_outlets? Am I doing it completely wrong? Thanks. -- Rob

3 3

Towards a compile option for macgem
by Mark Rada 22 Feb '11

22 Feb '11

Hey, I recently wrote a small plugin for rubygems that will use the MacRuby compiler to compile *.rb files when you install a gem. It is usable, but very simple right now; I would like to make it more powerful in a few different ways and I'm not sure which would be good. Things I think I could do (I have not looked at the rubygems source code in depth yet, so I'm not sure what I am allowed to do using the proper API): - A gemspec property (e.g. spec.compile_for_macruby = true) - A gem command: gem compile nokogiri gem compile —remove-original-files nokogiri • I can’t remove the original *.rb files and leave *.rbo files by default because of how rubygems identifies gems (unless I modify gemspec files) - A gem install option gem install —compile nokogiri I’m not sure which is best, perhaps all of them will get implemented, but I was wondering what the communities thoughts were about compiling gems; especially since the gemspec option won't work if the community never uses it. The repo is located at https://github.com/ferrous26/rubygems-compile -- Mark Rada mrada(a)marketcircle.com

4 4

NSLocalizedString
by Martin Hawkins 22 Feb '11

22 Feb '11

I'm taking a look at the Apple Sample code called PhotoSearch. In DateCell.m, there is a use of NSLocalizedString as follows: - (NSString *)todayString { return NSLocalizedString(@"Today", @"Today title string"); } I translated this as: def todayString return NSLocalizedString( "Today", "Today title string") end but got: DateCell.rb:217:in `todayString': undefined method `NSLocalizedString' for #<DateCell:0x200c86740> (NoMethodError) Changing the line to return NSBundle.mainBundle.localizedStringForKey("Today", value:"Today title string", table:nil) works but NSLocalizedString is supposed to be a Foundation Function, so should be 'freely' available in MacRuby, shouldn't it?

4 3

0.9 update
by Laurent Sansonetti 22 Feb '11

22 Feb '11

Hi guys, 0.9 is now ready to be released! (really!). The trunk branch has been copied as branches/0.9 and we will continue the development on trunk, which now uses the 0.10 version number. It would be nice if you could try the latest nightly build with your app and favorite Ruby lib, and let me know if you find anything wrong, as I had to change (again) the const lookup rules to fix a regression. yesterday. I did a bit of testing and I'm confident the fix is good, but I would prefer to see more testing. http://www.macruby.org/files/nightlies/macruby_nightly-2011-02-22.pkg If I don't hear anything bad, 0.9 will be released Friday :) Thanks, Laurent

2 1