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

[MacRuby] #167: Autoload throws an exception at the second call
by MacRuby 25 Nov '08

25 Nov '08

#167: Autoload throws an exception at the second call ----------------------------------------+----------------------------------- Reporter: vincent.isambart@… | Owner: lsansonetti@… Type: defect | Status: new Priority: critical | Milestone: Component: MacRuby | Keywords: ----------------------------------------+----------------------------------- The second call to autoload always throws an exception: {{{ ./miniruby -e 'autoload :A, "a";autoload :B, "b"' -e:1:in `autoload': wrong argument type NSObject (expected Data) (TypeError) from -e:1:in `<main>' }}} The first call to rb_autoload creates and saves an autoload_table, but it seems the type of the table (NSObject) is not what the second call to rb_autoload is waiting for (it wants a Data). The check is on the first line of check_autoload_table (all of those functions are in variable.c). -- Ticket URL: <http://www.macruby.org/trac/ticket/167> MacRuby <http://macruby.org/>

1 1

[MacRuby] #162: Lack of support of selectors in BridgeSupport
by MacRuby 24 Nov '08

24 Nov '08

#162: Lack of support of selectors in BridgeSupport ----------------------------------------+----------------------------------- Reporter: vincent.isambart(a)gmail.com | Owner: lsansonetti(a)apple.com Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: ----------------------------------------+----------------------------------- When I run http://pastie.org/315934 and I press a button the application crashes: http://pastie.org/315935 Laurent told it was because selectors are not yet supported in BridgeSupport. There is a work around specifying the signature of the callback with method_signature but we should not have to do it. -- Ticket URL: <http://www.macruby.org/trac/ticket/162> MacRuby <http://macruby.org/>

1 1

[MacRuby] #142: Infinite loop creating new Monitor object
by MacRuby 23 Nov '08

23 Nov '08

#142: Infinite loop creating new Monitor object ---------------------------------------+------------------------------------ Reporter: dev(a)petermcm.dircon.co.uk | Owner: lsansonetti(a)apple.com Type: defect | Status: new Priority: major | Milestone: MacRuby 0.3 Component: MacRuby | Keywords: ---------------------------------------+------------------------------------ Can't quite figure out how, but creating a new instance of a Monitor (std ruby lib) creates an infinite loop which eventually falls over with stack too deep. Looks like it's maybe an issue calling super from within a mixin, when the mixin is within a class which has no explicit superclass? {{{ > macruby -v MacRuby version 0.3 (ruby 1.9.0 2008-06-03) [universal-darwin9.0] > macruby -rmonitor -e 'Monitor.new' /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize': stack level too deep (SystemStackError) from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' ... 7263 levels... from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from /Library/Frameworks/MacRuby.framework/Versions/0.3/usr/lib/ruby/1.9.0/monitor.rb:207:in `initialize' from -e:1:in `new' from -e:1:in `<main>' }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/142> MacRuby <http://macruby.org/>

1 7

Re: [MacRuby-devel] Bindings only working one-way
by Michael Winterstein 22 Nov '08

22 Nov '08

> > for example: > attr_accessor :billy # will create setter and getter for billy with > all the appropritate KVO methods > > def updateMyValue(sender) #called from a button perhaps > setBilly(4) > end > > #or setValue:4 forKey:billy > > #@billy = 4 will not work, because it bypasses the accessor methods > > > So you don't need to override the accessors unless you are doing some > additional work. > > If you do override the accessors then you will have to put the whole > willChangeValueForKey, and didChangeValueForKey calls in your > overwritten method. > In your code below you do override the accessor, and therefore lose > the KVO. > > This turned out to be the key. The way to make it work automatically is just to use attr_accessor, but "setX(value)" within the program to modify it (even though that method isn't one you wrote). I had tried .= and self.X =, neither of which work, but that one does. It even works with the Matrix binding to selectedTags. I get the sense it may be trickier with something more complex or dynamic - which I may eventually want to do, but I'm happy with this for now. The trickier one was actually the Booleans. When you bind to a Boolean variable, it's now being set in a non-Ruby way. What that means is: something if X no longer works the way you'd expect - this is always true. Instead you need to do: something if X == true I know some people prefer the more explicit style anyways, and maybe that's one reason why. Or it could be considered a bug. As I understand it, the NS YES and NO are integer values which is sort of troublesome with the way Ruby treats 'false'. Thanks, Michael

1 0

Re: [MacRuby-devel] What's the best way to implement a delegate/action with multiple parameters?
by Michael Winterstein 22 Nov '08

22 Nov '08

> > Date: Fri, 21 Nov 2008 15:43:38 -0500 > From: Benjamin Stiglitz <ben(a)tanjero.com> > Subject: Re: [MacRuby-devel] What's the best way to implement a > delegate/action with multiple parameters? > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Message-ID: <49459A0D-1E87-4AE8-8709-3505B2C5173E(a)tanjero.com> > Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; > delsp=yes > >> I'm pretty new to Cocoa, so maybe I'm overlooking the obvious here. >> I just want to make sure I'm not doing more work than necessary. >> >> I'd like to be able to control the minimum size for a NSSplitView. >> As I understand it, I need to have a delegate with a method that can >> handle >> splitView:constrainMaxCoordinate:ofSubviewAt: >> >> So far that isn't supported using Interface Builder, is it? >> >> If I need to do it 'manually' - do I get a reference to the >> NSSplitView, and then tell it to set its delegate to something that >> responds to the method? When/where should I do this - in the Window >> Controller's AwakeFromNib or some other place? > > You can set the delegate in Interface Builder by ctrl-clicking from > the split view to the delegate object and clicking ?delegate? in the > resulting HUD popup. Then just implement that method on your delegate > object. > > If you haven?t already, be sure to check out the Delegates and Data > Sources guide at: > <http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaFundamentals… >> > > -Ben > Thanks. For some reason I was thinking of it backwards - trying to connect it up from my delegate to the SplitView, which doesn't make a whole lot of sense really. I also got it confused with actions. Wired it up and it works. -Michael

1 0

PBI - MacRuby aux Fines Merbs...
by Rich Morin 22 Nov '08

22 Nov '08

IMHO, MacRuby and Merb are two of the most interesting current developments in the Ruby arena. Because I've been looking at both of them, I started noticing some similarities, including: * Focus on design and engineering In an age of "cowboy programming", I find it refreshing to see that some programming projects actually embrace design and engineering. * large, well-documented APIs In a community dominated by a web framework (Rails) that has no defined API, I think this is quite noteworthy. * MVC-based UI frameworks Both MacRuby and Merb can both be used for purposes other than interactive UI development (eg, batch-mode applications, web services). However, their focus is on UI and both use an MVC-based approach (though the specifics vary markedly). Anyway, I started wondering whether any parts of Merb might be useful for MacRuby to consider adopting. For example: * Merb, like Rails, defines conventions for directory layout. Would it make sense for MacRuby to have similar conventions? * Merb stresses modularity very strongly, using gems to add "plugins", "slices", etc. What kinds of modularity should we encourage for MacRuby, HotCocoa, etc? * Some of Merb's plugins add functionality (eg, DataMapper) which might be useful in a MacRuby application. Would it be useful for MacRuby to be able to use Merb plugins? Comments solicited... -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm(a)cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development

6 10

Bindings only working one-way
by Michael Winterstein 22 Nov '08

22 Nov '08

I'm having difficulty working with bindings and I'm not sure if it's a MacRuby thing or my poor understanding of how they work. I've tried binding to two types of things - an NSMatrix of radio buttons (binding to "selectedTag") and a Checkbox value. Using just an attr_accessor - the variable changes when the user changes them, but changing the variable doesn't update in the UI. So I added an explicit setter method and to change the variable, I use self.setVideoSource(VID_USE_S2) to modify it. This works to change it on-screen, but now UI changes aren't getting through to the variables properly. The NSMatrix variable isn't changing, and the other variables are changing but are no longer Boolean. (If I do a "p x" I get either #<NSCFBoolean:0xa07f13f8> or #<NSCFBoolean:0xa07f1400>. I tried replacing 'attr_accessor' with 'attr_reader', and adding an explicit getter. That results in the following when I run (even if I add a 'return nil' to my setter method): [4169:10b] KVO autonotifying only supports -set<Key>: methods that return void. Autonotifying will not be done for invocations of - [MainWinController setVideoSource:]. I haven't yet tried manual notification because I'm not likely to use bindings for this case if that much work is required. Is this the expected way to go, or am I missing something here? Here's a bit of the code (these are set as keys in IB). When used elsewhere, I just have them as the instance variable : attr_accessor :audioIncludeS1 # whether to include audio attr_accessor :audioIncludeS2 # for a particular channel attr_accessor :videoSource # which source to use (if any) for video def setAudioIncludeS1(value) @audioIncludeS1 = value end def setAudioIncludeS2(value) @audioIncludeS2 = value end def setVideoSource(value) case value when VID_USE_S1 @videoSource = VID_USE_S1 when VID_USE_S2 @videoSource = VID_USE_S2 when VID_USE_NONE @videoSource = VID_USE_NONE else @videoSource = VID_USE_NONE end end

2 1

What's the best way to implement a delegate/action with multiple parameters?
by Michael Winterstein 21 Nov '08

21 Nov '08

I'm pretty new to Cocoa, so maybe I'm overlooking the obvious here. I just want to make sure I'm not doing more work than necessary. I'd like to be able to control the minimum size for a NSSplitView. As I understand it, I need to have a delegate with a method that can handle splitView:constrainMaxCoordinate:ofSubviewAt: So far that isn't supported using Interface Builder, is it? If I need to do it 'manually' - do I get a reference to the NSSplitView, and then tell it to set its delegate to something that responds to the method? When/where should I do this - in the Window Controller's AwakeFromNib or some other place?

2 1

KVO dot notation bug?
by Jim Getzen 20 Nov '08

20 Nov '08

I may have come across a KVO-related bug in MacRuby. In my project I have an Objective-C subclass of NSObject that uses @property and @synthesize to set up instance variable accessors. In the init method I set a key-value observer for one of those variables ('text') using: [self addObserver:self forKeyPath:@"text" options:NSKeyValueObservingOptionNew context:NULL]; The class also has the required observing method: - (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context When I set a new value for 'text' from Objective-C code using something like instance.text = @"Hello", the observing method is called as expected and everything is fine. When I set a new value from MacRuby code using instance.setText("Hello"), it also works fine. However, when I set a new value from MacRuby code using dot notation, e.g. instance.text = "Hello", it fails and the debugger is activated. The error log is lengthy, but it begins with these statements: warning: Could not find object file "/private/tmp/trunk/array.o" - no debug information available for "array.c". warning: Could not find object file "/private/tmp/trunk/bignum.o" - no debug information available for "bignum.c". Assigning values to the other instance variables of the Obj-C class works fine from MacRuby using dot notation, but those other variables do not have observers assigned. In fact, if I remove the 'observeValue...' method from the Obj-C class, the dot notation assignment works fine again for that 'text' variable. Sure seems like a bug to me. Any ideas? Jim

2 1

[MacRuby] #152: KVC arguments not properly marshalled
by MacRuby 14 Nov '08

14 Nov '08

#152: KVC arguments not properly marshalled -----------------------------+---------------------------------------------- Reporter: ben(a)tanjero.com | Owner: lsansonetti(a)apple.com Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: -----------------------------+---------------------------------------------- An argument isn’t being marshalled properly to mutable array KVC accessors. {{{ class KVCTest def initialize; @a = []; end def countOfThings; @a.size; end def objectInThingsAtIndex(i); @a[i]; end end KVCTest.new.valueForKey 'things' irb(main):015:0> KVCTest.new.valueForKey 'things' TypeError: no implicit conversion from nil to integer from (irb):11:in `[]' from (irb):11:in `objectInThingsAtIndex' from bin/irb:12:in `<main>' }}} Not sure why objectInThingsAtIndex: is getting a nil arg here. -- Ticket URL: <http://www.macruby.org/trac/ticket/152> MacRuby <http://macruby.org/>

1 6