March 2011 - macruby-tickets - lists.macosforge.org

[MacRuby] #1148: Procs used for Cocoa callbacks are being given class objects instance of the instance of the class
by MacRuby 29 Jun '11

29 Jun '11

#1148: Procs used for Cocoa callbacks are being given class objects instance of the instance of the class ------------------------------------+--------------------------------------- Reporter: mrada@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ------------------------------------+--------------------------------------- When I try to use a proc for a notification callback instead of a method, when the callback is made I am given the class object instead of the instance of the object. This example should work, but will not because when callback is called, it will be given the NSDictionary class constant instead of an instance of an NSDIctionary like I was supposed to get: framework 'Cocoa' callback = Proc.new { |notif| puts notif.userInfo.inspect } workspace = NSWorkspace.sharedWorkspace workspace.notificationCenter.addObserver callback, selector:'call:', name:NSWorkspaceDidLaunchApplicationNotification, object:nil workspace.launchAppWithBundleIdentifier 'com.apple.mail', options:NSWorkspaceLaunchAsync, additionalEventParamDescriptor:nil, launchIdentifier:nil NSRunLoop.currentRunLoop.runUntilDate( Time.now + 5 ) -- Ticket URL: <http://www.macruby.org/trac/ticket/1148> MacRuby <http://macruby.org/>

1 2

[MacRuby] #1119: Object initalize with a variable length argument shows up as a public method
by MacRuby 21 Jun '11

21 Jun '11

#1119: Object initalize with a variable length argument shows up as a public method ------------------------------------------+--------------------------------- Reporter: smorss@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ------------------------------------------+--------------------------------- I am running MacRuby 0.8. If I create a class with an initialize method that takes a variable length argument: class XX ; def initialize (*x) ; end ; end then "XX.new.methods" includes :initialize (to test this, try it in its own file or a new macirb session, so there are no other classes defined). initialize should not show up as a public method. If I try to call the method (e.g. "XX.new.initialize"), it has the proper behavior (says it can't, because initialize is private). If I create another XX instance, but pass a parameter, e.g. "XX.new(1).methods", :initialize goes away. If I call "XX.new.methods" again, :initialize is no longer there as well (feels like a Ruby class initialization problem). If I start from scratch and run the same line twice in the same session: class XX ; def initialize (*x) ; end ; end class XX ; def initialize (*x) ; end ; end then "XX.new.methods" no longer contains the initialize method (has the correct behavior). -- Ticket URL: <http://www.macruby.org/trac/ticket/1119> MacRuby <http://macruby.org/>

1 1

[MacRuby] #1212: Remove HotCocoa references from MacRuby
by MacRuby 27 May '11

27 May '11

#1212: Remove HotCocoa references from MacRuby -----------------------------------+---------------------------------------- Reporter: garysweaver@… | Owner: lsansonetti@… Type: defect | Status: new Priority: trivial | Milestone: Component: MacRuby | Keywords: hotcocoa cleanup -----------------------------------+---------------------------------------- The following hotcocoa references are still in the current MacRuby. Per Jordan Hubbard's suggestion, they should be removed: instruby.rb: when 'hotcocoa', 'rb_nibtool' misc/release/MacRuby.pmdoc/01macruby-contents.xml: .... (its a long line) ... rakelib/builder/options.rb: $stderr.puts "The 'build_as_embeddable' build configuration has been removed because it is no longer necessary. To package a full version of MacRuby inside your application, please use `macrake deploy` for HotCocoa apps and the `Embed MacRuby` target for Xcode apps." sample-macruby/About MacRuby Examples.rtf:\b HotCocoa sample-macruby/About MacRuby Examples.rtf:\b0 directory contains examples for the MacRuby's HotCocoa\ sample-macruby/Scripts/growl/hotcocoa_growl.rb:require 'hotcocoa' sample-macruby/Scripts/growl/hotcocoa_growl.rb: include HotCocoa sample-macruby/Scripts/growl/hotcocoa_sample.rb:require 'hotcocoa_growl' test-macruby/cases/hotcocoa/mapper_test.rb:require 'hotcocoa' test-macruby/cases/hotcocoa/mapper_test.rb: include HotCocoa::Mappings test-macruby/cases/hotcocoa/mappings_test.rb:require 'hotcocoa' test-macruby/cases/hotcocoa/mappings_test.rb: include HotCocoa test-macruby/cases/hotcocoa/object_ext_test.rb:require 'hotcocoa' test-macruby/cases/hotcocoa/object_ext_test.rb: assert_equal HotCocoa, Object.full_const_get("HotCocoa") test-macruby/cases/hotcocoa/object_ext_test.rb: assert_equal HotCocoa::Mappings, Object.full_const_get("HotCocoa::Mappings") test-macruby/cases/hotcocoa/plist_test.rb:require 'hotcocoa' test-macruby/cases/hotcocoa/plist_test.rb: include HotCocoa -- Ticket URL: <http://www.macruby.org/trac/ticket/1212> MacRuby <http://macruby.org/>

1 3

[MacRuby] #988: Unable to get rack::basic::auth to function as demonstrated via sinatra page.
by MacRuby 19 May '11

19 May '11

#988: Unable to get rack::basic::auth to function as demonstrated via sinatra page. ------------------------------+--------------------------------------------- Reporter: jhamor@… | Owner: joshua.ballanco@… Type: defect | Status: new Priority: critical | Milestone: Component: ControlTower | Keywords: ------------------------------+--------------------------------------------- While following the sinatra docs, i've tried all the possible combinations to get rack::basic::auth to function. When i use regular ruby-1.9 and sinatra 1.1.0 and rack 1.2.1, all seems well. When i switch back to macruby 0.7/controltower 1.0, i get a endless cycling of the basic authentication boxes and auth.credentials is some weird utf-8 string. Not really sure where to file this bug or what details are needed for reproduction, other than following the basic auth example for rack. Below works on ruby-1.9.2-p0/sinatra/rack: use Rack::Auth::Basic do |username, password| puts "user: #{username} pass: #{password}" username == 'admin' && password == 'secret' end Where this same example does not work on macruby/controltower. -- Ticket URL: <http://www.macruby.org/trac/ticket/988> MacRuby <http://macruby.org/>

1 6

[MacRuby] #1159: Control Tower needs logging
by MacRuby 12 May '11

12 May '11

#1159: Control Tower needs logging -------------------------------+-------------------------------------------- Reporter: pgibson@… | Owner: joshua.ballanco@… Type: defect | Status: new Priority: major | Milestone: Component: ControlTower | Keywords: logging -------------------------------+-------------------------------------------- Control Tower doesn't log any page hits right now. It would be pretty useful if it did. -- Ticket URL: <http://www.macruby.org/trac/ticket/1159> MacRuby <http://macruby.org/>

1 5

[MacRuby] #995: NoMethodError for initialization on MacRuby but works fine on CRuby
by MacRuby 05 May '11

05 May '11

#995: NoMethodError for initialization on MacRuby but works fine on CRuby ------------------------------------+--------------------------------------- Reporter: mrada@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ------------------------------------+--------------------------------------- When using the jiraSOAP gem (version 0.4.0) and I try to create a new JIRA::JIRAService object with #new I always get a NoMethodError on MacRuby, but when I run the gem in CRuby the initialization works fine. The source for the gem is on github at github.com/Marketcircle/jiraSOAP -- Ticket URL: <http://www.macruby.org/trac/ticket/995> MacRuby <http://macruby.org/>

1 7

[MacRuby] #854: Time and NSDate cannot be compared with Comparable operators
by MacRuby 05 May '11

05 May '11

#854: Time and NSDate cannot be compared with Comparable operators ----------------------------------+----------------------------------------- Reporter: massicotte@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- Time is now relatively equivalent to NSDate, but they cannot be compared with the Comparable operators. If compare: works, <=> should be implemented as well. $ macirb irb(main):001:0> date = NSDate.date => #<__NSCFDate:0x20023d3a0> irb(main):002:0> time = Time.now => 2010-08-17 16:28:46 -0700 irb(main):003:0> time < date ArgumentError: comparison of Time with __NSCFDate failed irb(main):005:0> date.compare(time) => -1 irb(main):006:0> time.compare(date) => 1 irb(main):007:0> -- Ticket URL: <http://www.macruby.org/trac/ticket/854> MacRuby <http://macruby.org/>

1 4

[MacRuby] #884: Abort occurs when calls Thread#value after throw an exception to a thread, Using 32bit arch.
by MacRuby 05 May '11

05 May '11

#884: Abort occurs when calls Thread#value after throw an exception to a thread, Using 32bit arch. ----------------------------------+----------------------------------------- Reporter: watson1978@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ----------------------------------+----------------------------------------- {{{ #!ruby # spec/frozen/core/thread/raise_spec.rb # it "can go unhandled" do t = Thread.new do loop {} end t.raise t.value }}} Result: {{{ $ DYLD_LIBRARY_PATH=. ./macruby -v -I./lib t.rb MacRuby 0.7 (ruby 1.9.2) [universal-darwin10.0, i386] terminate called after throwing an instance of 'RoxorThreadRaiseException*' zsh: abort DYLD_LIBRARY_PATH=. ./macruby -v -I./lib t.rb }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/884> MacRuby <http://macruby.org/>

1 2

[MacRuby] #1198: Kernel#framework method fails when a file in the current directory matches a framework name
by MacRuby 05 May '11

05 May '11

#1198: Kernel#framework method fails when a file in the current directory matches a framework name ----------------------------------+----------------------------------------- Reporter: christian@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: framework ----------------------------------+----------------------------------------- Kernel#framework can accept framework names like 'Cocoa', or paths, like '/System/Library/Frameworks/Cocoa.framework'. However, it distinguishes between the two forms naively, causing trouble when a file or directory in the current directory matches the name of any framework. For example, try this with MacRuby 0.9: {{{ # Works! $ macruby -e 'framework "Cocoa"' $ touch Cocoa $ macruby -e 'framework "Cocoa"' -e:1:in `<main>': framework at path `Cocoa' cannot be located (RuntimeError) }}} This has become a really annoying problem for me because XCode 4 creates separate directories for most targets. Thus, when you try to load your custom framework, the above failure occurs because Kernel#framework assumes it's found the framework and moves on. -- Ticket URL: <http://www.macruby.org/trac/ticket/1198> MacRuby <http://macruby.org/>

1 5

[MacRuby] #997: FIxnum.new gives a strange error on MacRuby
by MacRuby 04 May '11

04 May '11

#997: FIxnum.new gives a strange error on MacRuby ------------------------------------+--------------------------------------- Reporter: mrada@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: Component: MacRuby | Keywords: ------------------------------------+--------------------------------------- With Ruby 1.9.2 I am told that Fixnum does not have a method called #new, but MacRuby is telling me that I am passing the wrong number of arguments. irb(main):002:0> Fixnum.new ArgumentError: wrong number of arguments (0 for 0) -- Ticket URL: <http://www.macruby.org/trac/ticket/997> MacRuby <http://macruby.org/>

1 4