November 2010 - MacRuby-devel - lists.macosforge.org

converging for 1.0
by Laurent Sansonetti 01 Dec '10

01 Dec '10

Hi guys, Now that the vacations are behind us (well, behind me at least :)), it's time to focus on converging MacRuby for its first stable release, 1.0. My goal is to release it somewhere in 2011 (the sooner the better :)). In order to smoothly achieve that goal, it's also time to accelerate the current release system and improve the way we classify and address incoming bugs reports. After talking with the others committers we decided on the following: 1) Much more frequent releases Starting from now we will release more frequently. Until we reach 1.0, releases will mostly contain bug fixes and improvements, and practically no feature. As a matter of fact, I intend to release trunk as 0.8 next week. By releasing MacRuby more frequently we hope people will also test MacRuby more frequently, and report more bugs. 2) Better bug management We have too many bugs registered in the tracker, and it's a pain to manage all of them. Starting from now, we will classify all existing bugs as well as incoming ones in two categories: for 1.0 and for later. We will then only focus on bugs for 1.0. The second step is to reduce the problem into a small test case (if applicable) then attach the #reduction keyword. Once bugs are properly reduced, we can fix them more easily. We intend to attach a keyword to bugs that seem to be easy to fix, this way new comers can help and learn how MacRuby works. 3) Bug smash days We will organize bug smash days. They will happen on an IRC channel (details forthcoming). The first one will happen this saturday, 6th December. We will have people from 3 different time zones (US west coast, Europe and Japan) on the IRC channel, and our first task will be to start managing all the bugs, using the method described above. New comers are greatly welcomed and we will make sure everyone who wants to help can help. 4) Compatibility support page The big challenge for MacRuby 1.0 is to have excellent Ruby compatibility. We currently have 2 metrics to test our Ruby compatibility: RubySpec and Rails. However it's not enough, there are lots of Ruby libraries and C extensions around that we can't afford to test by ourselves. Therefore, we intend to prepare a webpage on the website that lists Ruby libraries that are known to work with MacRuby, and those who don't run yet. We will make sure the community can easily update that page. Having an updated list of libraries that we should run should help the team fixing compatibility bugs. That's all for now, bug if you have any suggestion on how to improve the current development process, please let us know. Laurent

11 13

Re: [MacRuby-devel] [MacRuby] #1002: AXUIElement functions won't accept Pointers of type :id
by William Siegrist 30 Nov '10

30 Nov '10

On Nov 30, 2010, at 12:14 PM, MacRuby wrote: > Comment(by martinlagardette@…): > > Can you check your macruby's revision? I think the latest build was built > before the patch was commited, but I don't know at what hour they are > built. > For the record, the nightlies are built around 1am (Pacific). And now that I think of that, it means the date that they are labeled with is the morning they were built, so calling them nightlies is a little misleading. In any case, the Last-Modified time should be within minutes of the build time, if that helps answer some questions: $ curl -I http://www.macruby.org/files/nightlies/macruby_nightly-latest.pkg ... Last-Modified: Mon, 29 Nov 2010 09:14:15 GMT $ curl -I http://www.macruby.org/files/nightlies/macruby_nightly-2010-11-27.pkg ... Last-Modified: Sat, 27 Nov 2010 09:13:54 GMT -Bill

1 0

Key Value Observing module
by Alan Skipp 29 Nov '10

29 Nov '10

I hope people don't mind me posting this bit of code to the list, but I hope it will be of some use to others and would also be interested to hear if the technique has any problems which I've not foreseen. Ruby has its own means of implementing the observer pattern, but as Key Value Observing (KVO) is so pervasive in cocoa, it would be good if it was easy to use. The module is an attempt at making KVO a bit more pleasant to use in macruby. The ideas have been adapted/stolen from here: https://gist.github.com/153676 The following is an example of how to have a block of code executed asynchronously every time a property of an instance variable changes self.add_observer_for_key_path('person.first_name', async:true) do |object,change| object.do_expensive_calculation #will not block main thread end A concern I do have is that the object which wants to receive KVO notifications holds an array of Observer objects. These Observer objects hold a reference to the object receiving the KVO notifications. Is this going to cause havoc with garbage collection? module KVO class Observer require 'dispatch' attr_reader :observee, :path def initialize(object, path, async, block, opts=0) @observee = object @path = path @async = async @block = block @observee.addObserver(self, forKeyPath:path, options:opts, context:nil) end def observeValueForKeyPath(path, ofObject:object, change:change, context:context) if @async Dispatch::Job.new { @block.call(object, change) } else @block.call(object, change) end end def cancel_observation @observee.removeObserver(self, forKeyPath:@path) end end def add_observer_for_key_path(path, async:async, &block) (@_observers_array_ ||= []) << Observer.new(self, path, async, block) end def add_observer_for_key_path(path, async:async, options:opts, &block) (@_observers_array_ ||= []) << Observer.new(self, path, async, block, opts) end def remove_observer_for_key_path(path) observer = @_observers_array_.find {|o| o.path == path && o.observee == self} if @_observers_array_ @_observers_array_.delete(observer) and observer.cancel_observation if observer end end

3 3

require module
by Alan Skipp 29 Nov '10

29 Nov '10

Hi everyone, This is just a quick query about using 'include' in an xcode project. When creating an instance of a class, a 'require' statement is not needed beforehand, but to include a module, you must first require it. #no need to require 'Foo' x = Foo.new # must require 'Bar' beforehand require 'bar' include Bar Should this behaviour be more consistent?

2 1

NSEvent MacRuby (updated)
by András Zalavári 29 Nov '10

29 Nov '10

(I'm not sure if the previous mail was sent otherwise sorry for the multiple posts) Hello, I'm new to MacRuby. I found an unexpected behavior of NSEvent. first of all in Cocoa [NSEvent mouseLocation] would return an NSPoint, with the mouse position. MacRuby NSEvent.mouseLocation return an NSPoint, but without the appropriate values. *irb(main):001:0> framework 'cocoa'* *2010-11-15 13:45:35.880 macruby[669:903] +[NSATSGlyphGenerator initialize] invocation. The class is deprecated.* *=> true* *irb(main):002:0> NSEvent.mouseLocation* *=> #<NSPoint **x=NaN y=NaN**>* * * it does not even work within a mouseUp method, with an NSEvent instance. I tried the same code on an iMac, and it returns the appropriate code, as a CGPoint. so there must be differences between the two. I even got this warning Message NSATSGlyphGenerator on the MacBook, which I dont on the iMac Please help figure out the solution! Thanks Andras Zalavari I'm using Macbook, and MacRuby 7.0... or 7.1? how to check the version of MacRuby t?

4 9

windowControllerDidLoadNib strangeness
by Tom Jordan 28 Nov '10

28 Nov '10

Hello, I'm encountering some weird behavior when trying to update a view using windowControllerDidLoadNib after loading in a persistent document. When I provide windowControllerDidLoadNib a single argument, as shown below (and required by the NSDocument class definition and in every example I've seen), Xcode says: `windowControllerDidLoadNib:': wrong number of arguments (1 for 0) (ArgumentError) If I don't provide any argument, it says: undefined method `windowControllerDidLoadNib' for #<MyDocument:0x200646660> (NoMethodError) *I've tried every combination of one or no args for both the method signature and "super" call on the next line, and I can't seem to get any different results.* This is my first time trying to get persistence going, but I've read a lot about it, and everything else is working well.. it saves and loads, but I can't seem to get this hook working to update the GUI upon loading. * * * * class MyDocument < NSDocument attr_accessor :loadedmodel, :root #outlet to model field of controller # Name of nib containing document window def windowNibName 'MyDocument' end # Document data representation for saving (return NSData) def dataOfType(type, error:outError) outError.assign(NSError.errorWithDomain(NSOSStatusErrorDomain, code:-4, userInfo:nil)) NSKeyedArchiver.archivedDataWithRootObject((a)root.model) end # Read document from data (return non-nil on success) def readFromData(data, ofType:type, error:outError) outError.assign(NSError.errorWithDomain(NSOSStatusErrorDomain, code:-4, userInfo:nil)) @loadedmodel = NSKeyedUnarchiver.unarchiveObjectWithData(data) end # Return lowercase 'untitled', to comply with HIG def displayName fileURL ? super : super.sub(/^[[:upper:]]/) {|s| s.downcase} end def windowControllerDidLoadNib(aController) super(aController) @root.model = @loadedmodel NSLog("model loaded") end end Regards, Tom Jordan

3 9

restclient gem with MacRuby
by Mark Rada 27 Nov '10

27 Nov '10

Hi, I'm using the nightly builds of MacRuby and have not been able to load the restclient gem. I always get an error: ArgumentError: invalid string transliteration But it doesn't really give me a good hint where to look to find the problem. I took a quick look at the source but nothing jumped out at me as being suspicious. Has anybody tried using this gem in the past and had similar problems or successes? Thanks, Mark

2 2

MacRuby in the Mac App Store
by Henry Maddocks 25 Nov '10

25 Nov '10

This clause... 2.24 Apps that use deprecated or optionally installed technologies (e.g., Java, Rosetta) will be rejected seems to prohibit MacRuby apps. Anyone know for sure? Henry

7 11

copied Proc objects cause crash when used as Objective-C blocks
by Alan Skipp 24 Nov '10

24 Nov '10

I've been attempting to get an objective-c framework to work with macruby and I believe I've found a bug in the way ruby Proc objects are copied when used as objective-c blocks. The copied block doesn't seem to persist correctly beyond the scope in which it was copied. It isn't deallocated, but calling it results in a crash. Typical error messages are: wrong type NSCFSet (expected Proc) (TypeError) wrong type NSRectSet (expected Proc) (TypeError) I'm guessing that there's a pointer to the wrong memory location? Here's the Objective-C implementation: @implementation TestBlock - (id)initWithBlock:(void (^)())aBlock; { [super init]; block = [aBlock copy]; NSLog(@"Block: %@", block); block(); return self; } - (void)callBlock; { NSLog(@"block: %@", block); block(); } @end Within 'initWithBlock:', the copied block can be invoked without error. Attempting to do so from 'callBlock', results in a crash. The test framework can be used without error when using objective-c. Here's the ruby controller code: @b = TestBlock.alloc.initWithBlock Proc.new { puts "hello from ruby"} # this next line is called from a different scope and causes the crash @b.callBlock 2010-11-19 08:41:06.620 CallObjectiveCBlocks[7046:a0f] Block: <__NSAutoBlock__: 0x200be74a0> hello from ruby 2010-11-19 08:41:20.011 CallObjectiveCBlocks[7046:a0f] block: <__NSAutoBlock__: 0x200be74a0> 2010-11-19 08:41:20.012 CallObjectiveCBlocks[7046:a0f] /Users/alan/Documents/programming/macruby/CallObjectiveCBlocks/build/Debug/CallObjectiveCBlocks.app/Contents/Resources/Controller.rb:21:in `call:': wrong type Array (expected Proc) (TypeError) from /Users/alan/Documents/programming/macruby/CallObjectiveCBlocks/build/Debug/CallObjectiveCBlocks.app/Contents/Resources/rb_main.rb:23:in `<main>'

3 5

Conforming to a protocol
by Martijn Walraven 23 Nov '10

23 Nov '10

Hi, I was wondering if there is any way to formally indicate a MacRuby class conforms to an Objective-C protocol. I encountered some code that uses conformsToProtocol: instead of respondsToSelector: as a check before invoking delegate methods, and the only way I could get a delegate written in MacRuby to work was to create an Objective-C class with the same name and specify the required protocols in the interface declaration there. Thanks, Martijn

5 11