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

[MacRuby] #529: Using a Proc as a ‘callback function’
by MacRuby 23 Mar '10

23 Mar '10

#529: Using a Proc as a ‘callback function’ -------------------------------------+-------------------------------------- Reporter: eloy.de.enige@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -------------------------------------+-------------------------------------- Some Cocoa methods, or C functions, take pointers to functions which can be used as callbacks. For instance, FSEventStreamCreate: http://bit.ly/8p70Yw. RubyCocoa, in conjunction with BridgeSupport, supported this by allowing the user to give a proc that would be used as the callback. MacRuby should support this too. Here's a spec example: {{{ describe "BridgeSupport" do it "bridges a proc to be used where a pointer to a callback function is required" do array = [5, 3, 2, 4, 1] proc = Proc.new do |x, y, context_pointer| context = context_pointer[0].chr + context_pointer[1].chr + context_pointer[2].chr x <=> y if context == 'foo' end array.sortUsingFunction(proc, context: 'bar') array.should == [5, 3, 2, 4, 1] array.sortUsingFunction(proc, context: 'foo') array.should == [1, 2, 3, 4, 5] end end }}} Don't know if this is feasible, but it would be great if the arguments given to the proc, like the context argument, were no Pointer objects, but the object they actually point to: {{{ describe "BridgeSupport" do it "bridges a proc to be used where a pointer to a callback function is required" do array = [5, 3, 2, 4, 1] proc = Proc.new do |x, y, context| x <=> y if context == 'foo' end array.sortUsingFunction(proc, context: 'bar') array.should == [5, 3, 2, 4, 1] array.sortUsingFunction(proc, context: 'foo') array.should == [1, 2, 3, 4, 5] end end }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/529> MacRuby <http://macruby.org/>

1 5

[MacRuby] #509: Beta 0.5 does not allow methods with more than 11 arguments
by MacRuby 26 Feb '10

26 Feb '10

#509: Beta 0.5 does not allow methods with more than 11 arguments -----------------------------------+---------------------------------------- Reporter: johnmacshea@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: -----------------------------------+---------------------------------------- With methods with more than 11 arguments MacRuby beta 0.5 crashes. Eg with 12 arguments: invalid argc 12 Abort trap BTW: this was not the case with 0.4 (I assume it is not a Ruby 1.9.x issue?) -- Ticket URL: <http://www.macruby.org/trac/ticket/509> MacRuby <http://macruby.org/>

1 3

[MacRuby] #423: #respond_to? returns true, actual method call raises NoMethodError
by MacRuby 23 Feb '10

23 Feb '10

#423: #respond_to? returns true, actual method call raises NoMethodError ---------------------------------+------------------------------------------ Reporter: ecin@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ framework 'Cocoa' a = NSMetadataQuery.new a.respond_to? :setPredicate # => true a.setPredicate # => NoMethodError: undefined method `setPredicate' for #<NSMetadataQuery:0x2002a1e20> a.setPredicate "a" # => RuntimeError: NSInvalidArgumentException: -[NSCFString generateMetadataDescription]: unrecognized selector sent to instance 0x2002309c0 -- Ticket URL: <http://www.macruby.org/trac/ticket/423> MacRuby <http://macruby.org/>

1 5

[MacRuby] #512: MacRuby misreports #initialize argument count in error messages
by MacRuby 23 Feb '10

23 Feb '10

#512: MacRuby misreports #initialize argument count in error messages -----------------------------------+---------------------------------------- Reporter: matthew@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: -----------------------------------+---------------------------------------- Given the following code, {{{ class A def initialize(a, b, c) end end A.new }}} '''Expected result (Ruby 1.9.1)''' {{{ArgumentError: wrong number of arguments (0 for 3)}}} '''Actual result (MacRuby 0.5b2)''' {{{ArgumentError: wrong number of arguments (0 for 1)}}} -- Ticket URL: <http://www.macruby.org/trac/ticket/512> MacRuby <http://macruby.org/>

1 2

[MacRuby] #284: [HotCocoa] start of NSUserDefaults mapping
by MacRuby 12 Feb '10

12 Feb '10

#284: [HotCocoa] start of NSUserDefaults mapping ---------------------------------+------------------------------------------ Reporter: dj2@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ Attached is the start of a mapping for NSUserDefaults. This adds in a [], []= and delete methods for accessing the options. -- Ticket URL: <http://www.macruby.org/trac/ticket/284> MacRuby <http://macruby.org/>

1 1

[MacRuby] #278: [HotCocoa] Update application builder to generate core data mom files
by MacRuby 12 Feb '10

12 Feb '10

#278: [HotCocoa] Update application builder to generate core data mom files ---------------------------------+------------------------------------------ Reporter: dj2@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ The attached patch will look for a "data_models" key in the build.yml directory. data_models: - data/**/*.xcdatamodel Each of the found .xcdatamodel files, the file will be compiled to a .mom file and placed in the build resources directory. -- Ticket URL: <http://www.macruby.org/trac/ticket/278> MacRuby <http://macruby.org/>

1 1

[MacRuby] #318: enable arbitrary properties in hotcocoa app Info.plist
by MacRuby 12 Feb '10

12 Feb '10

#318: enable arbitrary properties in hotcocoa app Info.plist -----------------------------------+---------------------------------------- Reporter: isaackearse@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: hotcocoa -----------------------------------+---------------------------------------- This patch enables adding extra key/string properties to the Info.plist for a hotcocoa application. All you need to do is add a properties hash to config/build.yml and the application builder will take the properties in the hash and append them to the applications Info.plist. The use case I had for this was that I wanted to run my app as an agent application. (no dock icon or top left menu). To do this I needed to add the key LSUIElement with a string value of "1" to the Info.plist Cheers, Isaac -- Ticket URL: <http://www.macruby.org/trac/ticket/318> MacRuby <http://macruby.org/>

1 1

[MacRuby] #473: setObjectValue does not set floats, integers in NSTextFields properly.
by MacRuby 12 Feb '10

12 Feb '10

#473: setObjectValue does not set floats, integers in NSTextFields properly. -----------------------------------+---------------------------------------- Reporter: johnmacshea@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: NSTextField, setObjectValue -----------------------------------+---------------------------------------- When using setObjectValue (NSControl) with MacRuby floats and integer, though they are a subclass of NSNumber,they are not properly set (copied?). For example in macirb: irb(main):001:0> framework "Cocoa" => true irb(main):002:0> tf = NSTextField.alloc.init => #<NSTextField:0x20024b5a0> irb(main):003:0> num = NSNumber.numberWithFloat(23.3) => 23.2999992370605 irb(main):004:0> tf.setObjectValue(num) => #<NSTextField:0x20024b5a0> irb(main):005:0> p tf.stringValue "0" => "0" irb(main):006:0> p num.superclass.superclass NSNumber => NSNumber irb(main):007:0> tf.setFloatValue(23.3) => #<NSTextField:0x20024b5a0> irb(main):008:0> p tf.stringValue "23.29999923706055" => "23.29999923706055" or, more simply: irb(main):013:0> tf.setObjectValue(23.3) => #<NSTextField:0x20024b5a0> irb(main):014:0> p tf.stringValue "0" => "0" To contrast with proper behavior, with the following obj C code: NSTextField *tf = [[NSTextField alloc] init]; NSNumber *num = [NSNumber numberWithFloat:23.3]; [tf setObjectValue:num]; NSLog(@"string value of tf %@", [tf stringValue]); results in the following: 2009-12-01 14:48:56.553 TextFieldSet[12012:a0f] string value of tf 23.3 -- Ticket URL: <http://www.macruby.org/trac/ticket/473> MacRuby <http://macruby.org/>

1 3

[MacRuby] #266: HotCocoa Add descriptions to standard rake tasks
by MacRuby 11 Feb '10

11 Feb '10

#266: HotCocoa Add descriptions to standard rake tasks ---------------------------------+------------------------------------------ Reporter: dj2@… | Owner: lsansonetti@… Type: enhancement | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ---------------------------------+------------------------------------------ The attached patch adds desc entries to the standard rake tasks. This allows macrake -T to list the available tasks. -- Ticket URL: <http://www.macruby.org/trac/ticket/266> MacRuby <http://macruby.org/>

1 1

[MacRuby] #300: HotCocoa toolbar doesn't always honour ordering of items
by MacRuby 11 Feb '10

11 Feb '10

#300: HotCocoa toolbar doesn't always honour ordering of items ---------------------------------+------------------------------------------ Reporter: dj2@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: HotCocoa NSToolbar ---------------------------------+------------------------------------------ If you have a toolbar and use a mix of default symbols and NSToolbarItems then the toolbar will not maintain the ordering specified. All of the symboled items will move to the left of the toolbar and all the NSToolbarItems will be on the right. The attached patch fixes this issue. -- Ticket URL: <http://www.macruby.org/trac/ticket/300> MacRuby <http://macruby.org/>

1 1