September 2009 - MacRuby-devel - lists.macosforge.org

Seeing methods of extended ObjC objects in IB
by b.ohr 09 Sep '09

09 Sep '09

Hey guys, I added the MacRuby framework to an existing project (gitx on github, which uses GC also fortunately). After setting the build to compile 64bit only everything (-1, see below) works fine, so far I can say now. I am impressed! I defined my own controller in Ruby, call methods of it from the user interface and connected this controller to other ObjC-objects and call methods of them. But one thing does not work: If I extend an existing ObjC-Object, f.e. class PBGitHistoryController def do_what(sender) puts "do what?" end end then I don't see this method in the Interface Builder under 'Received Actions'. Is it my fault our yours? If I 'p' this object it says: #<NSKVONotifying_PBGitHistoryController:0x8002bd820> Perhaps this (KVO) is the problem? -- But let me say again: I like the MacRuby project so much and I wish I could use it for real development in the near future! Bernd

2 1

bundle or dylib
by Clay Bridges 09 Sep '09

09 Sep '09

Hi gang, I was checking out the potential changes to the website, particularly create-an-objective-c-bundle.txt, and that inspired me to ask a longstanding question. I know very little about this stuff, but from what I could discern, it looks like MacRuby is loading what are technically dylibs, and not proper bundles. Is this true, or am I just whack again? Thanks Clay

3 3

rescue NSException?
by Clay Bridges 09 Sep '09

09 Sep '09

Does MacRuby 0.5 rescue Objective-C NSExceptions? e.g. begin # call to Objective C dynlib here, raises NSException rescue # should this get called? end Thanks Clay

2 2

BridgeSupport and Parameter Errors
by Edward Hynes 09 Sep '09

09 Sep '09

I'm trying to re-implement the PlaySoftMIDI example from the Xcode installation in MacRuby, but am getting parameter errors. Could some kind soul point me in the right direction? Below is a small example that ends with a parameter error. The call to NewAUGraph appears to work, returning a zero, but the call to AUGraphAddNode returns -50. framework 'AudioToolbox' framework 'AudioUnit' load_bridge_support_file 'bridgesupport/Application.bridgesupport' load_bridge_support_file 'bridgesupport/AudioToolbox.bridgesupport' load_bridge_support_file 'bridgesupport/AudioUnit.bridgesupport' outGraph = Pointer.new_with_type '^{OpaqueAUGraph}' result = NewAUGraph outGraph # returns 0 puts result cd = ComponentDescription.new cd.componentManufacturer = KAudioUnitManufacturer_Apple cd.componentType = KAudioUnitType_MusicDevice cd.componentSubType = KAudioUnitSubType_DLSSynth cd_ptr = Pointer.new_with_type '{ComponentDescription=IIIII}' cd_ptr.assign cd synthNode = Pointer.new_with_type 'i' result = AUGraphAddNode outGraph[0], cd_ptr, synthNode # returns -50 puts result I generated the bridge support files with gen_bridge_metadata -f AudioToolbox -o AudioToolbox.bridgesupport gen_bridge_metadata -f AudioUnit -o AudioUnit.bridgesupport The Application.bridgesupport file contains struct and cftype definitions for ComponentDescription. They were generated using a header file since I couldn't figure out how to generate them from the CarbonCore framework directly. Any help would be appreciated. Thanks, Ed

1 0

NSTask writeData confusion
by Kristofer Joseph 09 Sep '09

09 Sep '09

I am hoping someone can tell me why my task isn't returning data to the stdoutput when I send commands via writeData. I am able to create a task and receive initial output when I launch the task, but when I try to send commands via writeData calls through my stdinput pipe the task never returns more data. I've attached the fdb program so you can drop it in your path, change the launchPath var and try it your own self. Source: class ApplicationDelegate attr_accessor :runButton, :continueButton, :stepButton, :quitButton attr_accessor :debugText def awakeFromNib @debugText.setString("") end def applicationDidFinishLaunching(notification) #Initialize envionment variable references defaultEnvironment = NSProcessInfo.processInfo.environment environment = NSMutableDictionary.alloc.initWithDictionary(@defaultEnvironment) #Path to the executatble launchPath = "/Applications/Adobe\ Flash\ Builder\ Beta/sdks/3.4.0/bin/fdb" #Create a reference to the notification center for listening on notifications @center = NSNotificationCenter.defaultCenter #Create Task @fdb = NSTask.new #Add an observer for the NSTaskDidTerminateNotification @center.addObserver(self,selector:"taskDead:",name:"NSTaskDidTerminateNotification",object:@fdb ) @fdb.setLaunchPath(launchPath) #Set up the environment environment.setObject("YES",forKey:"NSUnbufferedIO") @fdb.setEnvironment(environment) #Create output pipe @outputPipe = NSPipe.new @outputHandle = @outputPipe.fileHandleForReading @center.addObserver(self,selector:"taskDataAvailable:",name:"NSFileHandleReadCompletionNotification",object:@outputHandle ) @fdb.setStandardOutput(@outputPipe) #Create error pipe @errorPipe = NSPipe.new @errorHandle = @errorPipe.fileHandleForReading @center.addObserver(self,selector:"errorDataAvailable:",name:"NSFileHandleReadCompletionNotification",object:@errorHandle ) @fdb.setStandardError(@errorPipe) #Create input pipe @inputPipe = NSPipe.new @inputHandle = @inputPipe.fileHandleForWriting @fdb.setStandardInput(@inputPipe) #Launch that puppy @fdb.launch #Set the outputs to read in the background and notify asynchronously @outputHandle.readInBackgroundAndNotify @errorHandle.readInBackgroundAndNotify #Release the memory allocations for discarded objects @environment.release end def taskDataAvailable(notification) data = notification.userInfo.valueForKey(NSFileHandleNotificationDataItem) if !data.nil? string = NSString.alloc.initWithData(data,encoding:NSASCIIStringEncoding) self.parseDataString(string) @outputHandle.readInBackgroundAndNotify end end def errorDataAvailable(notification) data = notification.userInfo.valueForKey(NSFileHandleNotificationDataItem) if !data.nil? string = "ERROR: " string += NSString.alloc.initWithData(data,encoding:NSASCIIStringEncoding) self.parseDataString(string) @errorHandle.readInBackgroundAndNotify end end def parseDataString(dataString) @debugText.textStorage.mutableString.appendString(dataString) @debugText.setTextColor(NSColor.whiteColor) end def run(sender) puts "RUN" @inputHandle.writeData("r\n",dataUsingEncoding:NSString.defaultCStringEncoding) end def contiune(sender) puts "CONTINUE" @inputHandle.writeData("c\n",dataUsingEncoding:NSString.defaultCStringEncoding) end def step(sender) @inputHandle.writeData("s\n",dataUsingEncoding:NSString.defaultCStringEncoding) end def exit(sender) @inputHandle.writeData("quit\n",dataUsingEncoding:NSString.defaultCStringEncoding) self.killTask end def applicationShouldTerminateAfterLastWindowClosed(application) return true end def killTask if @fdb.isRunning @fdb.terminate end end def taskDead(notification) exitCode = notification.object.terminationStatus if exitCode != 0 puts "Task exited with code " + exitCode.to_s + " probably not a good thing." end @center.removeObserver(self) puts "Task died dude." end end

1 0

Globbed method arguments (splat) Limit
by John-Paul Bader 09 Sep '09

09 Sep '09

Hey guys, a friend of mine implemented a heap in ruby for educational purposes. He did so with several implementations. He had a few benchmarks and I suggested to run them on macruby to see how well it would hold up. Unfortunately we didn't get really far because apparently there is a problem with globbed/splatted method arguments in macruby which raises an exception if more than 199 arguments are passed. Can be tested easily with: def foo(*bar); puts bar.length;end 1.upto(1000) {|x| foo(*([0]*x))} In vm.cpp:2977 #define MAX_DISPATCH_ARGS 200 is defined and a big fat todo is right below it addressing this issue. Now I know its not a super urgent problem because its not what you do in ruby every day. Still its obviously something that has to change. In line 3003 there is this assert: assert(real_argc + count < MAX_DISPATCH_ARGS); so it must be important i guess. So i'm just wondering why it is limited to 200 in the first place and if there is something I can to even though I'm not really a capable (objective) c programmer ? After commenting out the code with the globbed arguments the benchmarks on the remaining tests ran a bit slower than on ruby 1.9.1. Kind regards, John

2 2

kvo vs referenced hash
by Matt Aimonetti 09 Sep '09

09 Sep '09

Hi list, Coming from a Ruby background, I try to understand and pick the best from Obj-C/Cococa and learn how to use brilliant ideas to improve my coding. Tonight I was working on a simple demo app to learn how things are done in the Obj-C world and see how they would transpose to the MacRuby world. Everything went well until the KVO question came along. Let's say I have a controller that we are going to call *Brain*. We also have a lot of simpler objects that don't do anything but having a state and being displayed, we are going to call them *Task instances*. The brain is called every X seconds to "*think*". My understanding is that an Obj-C developer would register all the tasks instance with the brain using a KVO and the brain would send notifications when it's being called to "think". So, every time a new task is being created, an observer is added on the brain with the new task key. Each Task instance has an observeValueForKeyPath:ofObject:change:context: method implemented which checks that the notification is meant for itself and if it is, to act accordingly. While the concept is simple and attractive. I wonder if it wouldn't be simpler to forget about kvo's and simply keep the list of registered tasks in the brain and the brain would call the tasks directly and tell them to change. It sounds to me that in the MacRuby world, it would be more efficient. If we have 250 tasks for instance, when a notification is being sent, every single task in the 250 tasks created, will receive the notification and will check what to do with it. If we had a simple hash/dictionary in the brain, we could directly find the task to handle and call it directly without having to go through the 250. Am I missing something or in this specific case and because we use Ruby, KVO aren't the way to go? Thanks for your help, - Matt

3 4

Help with QT syntax
by Martin Hawkins 07 Sep '09

07 Sep '09

I've been going through the MyRecorder example in the QTKit Capture Programming Guide (which works fine) but am having problems with the MacRuby syntax for the following: - (void)captureOutput:(QTCaptureFileOutput *)captureOutput didFinishRecordingToOutputFileAtURL:(NSURL *)outputFileURL forConnections:(NSArray *)connections dueToError:(NSError *)error I'd be very grateful if someone could point me in the right direction. Thanks

2 2

weird behavior in macirb in forwarder classes
by Carlo Cabanilla 05 Sep '09

05 Sep '09

Hi, I'm Carlo, I'm new to MacRuby and I'd like to contribute if possible. I found this weird bug when requiring modules that define classes that extend Forwardable and define delgates: $ echo "require 'csv'; puts 'good'" | macirb require 'csv'; puts 'good' NameError: undefined local variable or method `str' for CSV::Row:Class from 0:in `def_delegator:' But requiring it from a script works fine: $ macruby -e "require 'csv'; puts 'good'" good Same behavior for rss/parser: $ echo "require 'rss/parser'; puts 'good'" | macirb require 'rss/parser'; puts 'good' NameError: undefined local variable or method `str' for RSS::Parser:Class from 0:in `def_delegator:' $ macruby -e "require 'rss/parser'; puts 'good'" good I traced it to the def_instance_delegator method in Forwardable: def def_instance_delegator(accessor, method, ali = method) str = %Q{ def #{ali}(*args, &block) #{accessor}.send(:#{method}, *args, &block) end } # If it's not a class or module, it's an instance begin module_eval(str) rescue instance_eval(str) end end I found that if I just hard code the str value as the parameters to module_eval and instance_eval, it works: def def_instance_delegator(accessor, method, ali = method) # If it's not a class or module, it's an instance begin module_eval(%Q{ def #{ali}(*args, &block) #{accessor}.send(:#{method}, *args, &block) end }) rescue instance_eval(%Q{ def #{ali}(*args, &block) #{accessor}.send(:#{method}, *args, &block) end }) end end This is kind of hack, so I'm assuming the root cause has to do with how macirb treats variable scope? Is this a known bug? Can I help somehow? -- .Carlo

2 1

[MacRuby] #327: patch: Update .gitignore
by MacRuby 05 Sep '09

05 Sep '09

#327: patch: Update .gitignore -------------------------+-------------------------------------------------- Reporter: dev@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: -------------------------+-------------------------------------------------- add files generated with rake and rake install -- Ticket URL: <http://www.macruby.org/trac/ticket/327> MacRuby <http://macruby.org/>

1 1