[MacRuby-devel] macruby or macirb bug
In macirb the following code crashes >> array = NSMutableArray.arrayWithObjects([1,2]) => [[1, 2], 1511869] >> array => [[1, 2], 1511869] >> array.length => 2 >> array2 = NSMutableArray.arrayWithObjects([1, 2, "this"]) Killed Using the more ruby friendly way of assigning a variable to an array works. >> array = [1,2,"this"] =>[1, 2, "this"] ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] I tried converting a working script rubycocoa script to macruby and it failed on this line...
NSDistributedNotificationCenter.defaultCenter.addObserver_selector_name_object(self, :next_number, "next number", "com.imasender") #Working RubyCocoa line NSDistributedNotificationCenter.defaultCenter.addObserver self, selector: :next_number, name: "next number", object: "com.imasender" #But gives the error below when converted to MacRuby grammer and run with macruby. 2008-12-11 21:45:43.448 macruby[66187:10b] *** -[Receiver next_number]: unrecognized selector sent to instance 0x1319720 receiver.rb:29:in `run': NSInvalidArgumentException: *** -[Receiver next_number]: unrecognized selector sent to instance 0x1319720 (RuntimeError) from receiver.rb:29:in `' It's driving me crazy. If the statement is a correct translation from RubyCocoa to MacRuby syntax why am I getting a "unrecognized selector sent to..." error? ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] I tried converting a working script rubycocoa script to macruby and it failed on this line...
Thanks Vincent, You're suggestion fixed the script. The top line is the original rubycocoa line and the line below the macruby equivalent. It would be nice to add such an example to the tutorial at http://www.macruby.org/trac/wiki/MacRubyTutorial (please kind maintainer--if you are listening). It is not obvious that macruby would require quotes and a trailing colon when passing the name of a selector/method. I don't think there are any examples that cover this rule currently. Thanks, Tim center.addObserver_selector_name_object(self, :next_number, "next number", "com.imasender") #rubycocoa center.addObserver self, selector: "next_number:", name: "next number", object: "com.imasender" #macruby On Fri, Dec 12, 2008 at 7:00 AM, wrote: > Send MacRuby-devel mailing list submissions to >[email protected] > > To subscribe or unsubscribe via the World Wide Web, visit >http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > or, via email, send a message with subject or body 'help' to >[email protected] > > You can reach the person managing the list at >[email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. I tried converting a working script rubycocoa script to > macruby and it failed on this line... (Tim Rand) > 2. Re: I tried converting a working script rubycocoa script to > macruby and it failed on this line... (Vincent Isambart) > > > -- > > Message: 1 > Date: Thu, 11 Dec 2008 21:55:04 -0800 > From: "Tim Rand" > Subject: [MacRuby-devel] I tried converting a working script rubycocoa >script to macruby and it failed on this line... > To: [email protected] > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > > NSDistributedNotificationCenter.defaultCenter.addObserver_selector_name_object(self, > :next_number, "next number", "com.imasender") #Working RubyCocoa line > >NSDistributedNotificationCenter.defaultCenter.addObserver self, > selector: :next_number, name: "next number", object: "com.imasender" #But > gives the error below when converted to MacRuby grammer and run with > macruby. > > 2008-12-11 21:45:43.448 macruby[66187:10b] *** -[Receiver next_number]: > unrecognized selector sent to instance 0x1319720 > receiver.rb:29:in `run': NSInvalidArgumentException: *** -[Receiver > next_number]: unrecognized selector sent to instance 0x1319720 > (RuntimeError) >from receiver.rb:29:in `' > > It's driving me crazy. If the statement is a correct translation from > RubyCocoa to MacRuby syntax why am I getting a "unrecognized selector sent > to..." error? > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.macosforge.org/pipermail/macruby-devel/attachments/20081211/c96e3235/attachment-0001.html > > > > -- > > Message: 2 > Date: Fri, 12 Dec 2008 15:05:18 +0900 > From: "Vincent Isambart" > Subject: Re: [MacRuby-devel] I tried converting a working script >rubycocoa script to macruby and it failed on this line... > To: "MacRuby development discussions." > > Message-ID: ><[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > > NSDistributedNotificationCenter.defaultCenter.addObserver self, > > selector: :next_number, name: "next number", object: "com.imasender" #But > > gives the error below when converted to MacRuby grammer and run with > > macruby. > > > > It's driving me crazy. If the statement is a correct translation from > > RubyCocoa to MacRuby syntax why am I getting a "unrecognized selector > sent > > to..." error? > > I think your selector should not be :next_number but 'next_number:' > (note the ':' at the end). Every method that has a parameter should > have its selector ending with a ':' in MacRuby. > > Cheers, > Vincent > > > -- > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > End of MacRuby-devel Digest, Vol 10, Issue 17 > * > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] Am I the only one having problems with macgem in macruby 0.4?
I know problems with macgem have been posted (several times) before, but I can't tell from the threads whether or not gems are working in macruby version 0.4. It doesn't seem to work for me. Though 'sudo macgem query --remote' works as expecteed. Even if I run macruby version 0.3, gem installation fails, though it appears to have a different reason for failing, and version 0.3 can't even query remotely like 0.4 can. See the bottom of this email for the terminal output from the macruby version 0.3 attempt. It would be great if I could get sqlite3-ruby gem working with any version of macruby. Any advice is appreciated. Thanks, Tim > sudo macgem install sqlite3-ruby Bulk updating Gem source index for: http://gems.rubyforge.org/ /Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/1.9.0/yaml.rb:133: [BUG] Segmentation fault MacRuby version 0.4 (ruby 1.9.0 2008-06-03) [universal-darwin9.0, x86_64] -- stack frame (0xc08120060): 0004 0001 (0xc08120068): 0002 (0xc08120070): 0004 0003 (0xc08120078): 0004 (0xc08120080): 8004951e0 0005 (0xc08120088): 8004c45e0 0006 (0xc08120090): 0004 0007 (0xc08120098): 0004 0008 (0xc081200a0): 0009 (0xc081200a8): 800453c60 0010 (0xc081200b0): 8004c45e0 0011 (0xc081200b8): 80045c2e0 0012 (0xc081200c0): 800378640 0013 (0xc081200c8): 0004 0014 (0xc081200d0): 0004 0015 (0xc081200d8): 0016 (0xc081200e0): 800378640 0017 (0xc081200e8): 8003c3980 0018 (0xc081200f0): 0004 0019 (0xc081200f8): 0004 0020 (0xc08120100): 0021 (0xc08120108): 0004 0022 (0xc08120110): 8003c3980 0023 (0xc08120118): 8004b8ce0 0024 (0xc08120120): 800587860 0025 (0xc08120128): 80050b440 0026 (0xc08120130): 0027 (0xc08120138): 800587860 0028 (0xc08120140): 800949220 0029 (0xc08120148): 0004 0030 (0xc08120150): 0031 (0xc08120158): 0004 0032 (0xc08120160): 8009c61c0 0033 (0xc08120168): 800bb9f60 0034 (0xc08120170): 0001 0035 (0xc08120178): 0004 0036 (0xc08120180): 0004 0037 (0xc08120188): 0038 (0xc08120190): 800bba160 0039 (0xc08120198): 0004 0040 (0xc081201a0): c0821fd08 0041 (0xc081201a8): 80009ee00 0042 (0xc081201b0): 800bba640 0043 (0xc081201b8): 0004 0044 (0xc081201c0): 0004 0045 (0xc081201c8): c08120188 (= 37) 0046 (0xc081201d0): 800bba640 0047 (0xc081201d8): 80009ee00 0048 (0xc081201e0): 80092f100 0049 (0xc081201e8): 804312b40 0050 (0xc081201f0): 80425e040 0051 (0xc081201f8): 0004 0052 (0xc08120200): 80383b120 0053 (0xc08120208): 8044c7da0 0054 (0xc08120210): 0004 0055 (0xc08120218): c0821fb48 0056 (0xc08120220): 801e93c40 0057 (0xc08120228): 0002 0058 (0xc08120230): 0004 0059 (0xc08120238): 0004 0060 (0xc08120240): 0004 0061 (0xc08120248): 0004 0062 (0xc08120250): 0004 0063 (0xc08120258): 803687860 0064 (0xc08120260): 104da3f80 0065 (0xc08120268): 8032f8020 0066 (0xc08120270): 0067 (0xc08120278): 0068 (0xc08120280): 0069 (0xc08120288): 0070 (0xc08120290): 8009300a0 0071 (0xc08120298): 0004 0072 (0xc081202a0): 0002 0073 (0xc081202a8): 0004 0074 (0xc081202b0): 0004 0075 (0xc081202b8): 0076 (0xc081202c0): 0004 0077 (0xc081202c8): 0078 (0xc081202d0): 0004 0079 (0xc081202d8): 0080 (0xc081202e0): 8008e5040 0081 (0xc081202e8): 8032f8020 0082 (0xc081202f0): 8008dee80 0083 (0xc081202f8): 8009300a0 0084 (0xc08120300): 0004 0085 (0xc08120308): 0086 (0xc08120310): 104da0dd0 0087 (0xc08120318): 8032f8020 0088 (0xc08120320): 0004 0089 (0xc08120328): 0004 0090 (0xc08120330): 0004 0091 (0xc08120338): 0092 (0xc08120340): 0004 0093 (0xc08120348): 8032f8020 0094 (0xc08120350): 800841e80 0095 (0xc08120358): 0004 0096 (0xc08120360): c0821f7c8 0097 (0xc08120368): 800839de0 0098 (0xc08120370): 0004 0099 (0xc08120378): c08120338 (= 91) 0100 (0xc08120380): 0004 0101 (0xc08120388): 800839de0 0102 (0xc08120390): 8032f8020 0103 (0xc08120398): 0004 0104 (0xc081203a0): 80075a9c0 0105 (0xc081203a8): 0004 0106 (0xc081203b0): 8007505c0 0107 (0xc081203b8): 104d965f0 0108 (0xc081203c0): 800839de0 0109 (0xc081203c8): 800759f00 0110 (0xc081203d0): 0004 0111 (0xc081203d8): 80073e4e0 0112 (0xc081203e0): 104d9a630 0113 (0xc081203e8): 0004 0114 (0xc081203f0): 800744660 0115 (0xc081203f8): 104d9a630 0116 (0xc08120400): 800839de0 0117 (0xc08120408): 0004 0118 (0xc08120410): 80073e4e0 0119 (0xc08120418): 0004 0120 (0xc08120420): 0004 0121 (0xc08120428): 800744660 0122 (0xc08120430): 0004 0123 (0xc08120438): 800839de0 0124 (0xc08120440): 0004 0125 (0xc08120448): 0004 0126 (0xc08120450): 0127 (0xc08120458): 0004 0128 (0xc08120460): 0129 (0xc08120468): 8007446c0 0130 (0xc08120470): 800839de0 0131 (0xc08120478): 0004 0132 (0xc08120480): 0133 (0xc08120488): 0004 0134 (0xc08120490): 0004 0135 (0xc08120498): 0004 0136 (0xc081204a0): 0004 013
[MacRuby-devel] hotcocoa - can't find executable...how to find it
>> $:.each{|path| puts path + "/" + "hotcocoa.rb" if File.exists?(path + "/"
+ "hotcocoa.rb")}
/Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/1.9.0/hotcocoa.rb
$: is a ruby environmental variable for an array of all the paths that ruby
looks at to require a file.
Another useful one to know is $", which holds the names of all currently
loaded external files.
I would imagine that somehow the path setting has been altered or you
accidentally moved hotcocoa to a location not included in the $: set.
I am frustrated that macgem is not functioning too. There are a lot of
possible reasons for it, but the most likely seems to be that many of the
gems for older versions of ruby need to be updated to work with 1.9, the
version that macruby is based on. Alternatively, failure of any given gem to
load could be due to macruby being under development and yet incomplete.
For me getting certain gems like sqlite3 to funciton with macruby is a
necessity.
Perhaps wonderful Laraunt or someone else could share some of his/her wisdom
on this issue of why many gems don't work, and if there is a plan for how to
fix it. Otherwise, I am going to keep plugging away at it in my spare
time--maybe around 2050 or so I will solve it. But I will solve it
eventually, because I love the idea of macruby and I love my old gem library
and I can't live without either.
Tim
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] µgem (notice I am using your G reek character!) question
Hi Matt, First of all, thank you so much for working on the gem issue with macruby. There is no more important work in the world, er universe, right now than this--I mean it, from the bottom of my frustrated-at-not-being-able-to-use-sqlite3-heart. I am hoping you could comment on why sqlite3-ruby seems to install, but still isn't functional. Here is how I did with my first try at using µgem. 1. Installing rake via µgem appears to have worked! (this is hard to verify because "require 'rake'" works in macirb even before installing with µgem). 2. Installing sqlite3 via µgem seems to have worked! (BUT "require 'sqlite3'" STILL FAILS in macirb). How do you test gems installed via µgem? Where do they install to? Does that path need to be added to the $: for macirb to find them? Sorry for the basic questions... Thanks, Tim Here is my terminal screen: Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> sudo ./µgem install rake [info] Installing `rake-0.8.3' Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> which rake /usr/bin/rake Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> macgem which rake /Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/1.9.0/rake.rb Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> sudo ./µgem install sqlite3-ruby Password: [info] Installing `sqlite3-ruby-1.2.4' Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> macgem which sqlite3 Can't find sqlite3 Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> macgem which sqlite3-ruby Can't find sqlite3-ruby Tim:~/Documents/References/Technical/Ruport Book and pics/microgem/bin> macgem query --local *** LOCAL GEMS *** alloy-microgem (0.2.0) ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] Project status, goals, and other
> The macruby website has a timeline for project goals. Here is the link http://www.macruby.org/trac/wiki/MacRubyRoadmap I am very excited that the IO rewrite is on the chopping block for 0.5. Tim ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] Can any kind macruby experts help me get sqlite3 gem working with macruby--please?
Can any kind macruby experts help me get sqlite3 gem working with macruby?
sqlite3-ruby-1.2.4 ruby gem works in ruby 1.9.0. So I think it should work
in macruby also...
>From macirb I added the path to the gem:
$: << "path/to/the/sqlite3-ruby-1.2.4/lib"
require 'sqlite3.rb' # => true
$db = SQLite3::Database.new("/path/to/x.db.rsd")
RuntimeError: *no driver for sqlite3 found*
the error comes from the load_driver method near line 621 of the
sqlite3/database.rb file.
def load_driver( driver )
case driver
when Class
# do nothing--use what was given
when Symbol, String
require "sqlite3/driver/#{driver.to_s.downcase}/driver"
driver = SQLite3::Driver.const_get( driver )::Driver
else
[ "Native", "DL" ].each do |d|
begin
require "sqlite3/driver/#{d.downcase}/driver"
driver = SQLite3::Driver.const_get( d )::Driver
break
rescue SyntaxError
raise
rescue ScriptError, Exception, NameError
end
end
raise "no driver for sqlite3 found" unless driver
end
@driver = driver.new
end
private :load_driver
Macruby enters the method with driver set to NSNull, and the driver fails to
load. In ruby (1.9.0) the driver loads via the Native driver.
irb19 session:
>> db = SQLite3::Database.new("/Users/Tim/Desktop/newdb")
=> #,
@statement_factory=SQLite3::Statement,
@handle=#, @closed=false,
@results_as_hash=false, @type_translation=false, @translator=nil,
@transaction_active=false>
Can anyone offer an idea about how they might try to patch this to work with
macruby? I know an alternative would be CoreData--but it is too cumbersome
for me.
Thanks,
Tim
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] macruby and sqlite3 gem
I was worried that it was an IO issue with macruby, which is why I am very excited that the 0.5 version is going to be address the IO system--hopefully it will help with this issue. I would love to help, but an issue spanning macruby, obj-c, sqlite3, and possibly C is really stretching my abilities. On the subject of sqlite wrappers in objective-C. I tried several that I found on the sqlite webpage (the have a long list of wrappers in several languages including obj-c). But it appears that most if not all are not being maintained and are not up to date and don't work with Leopard. If anyone knows of a light weight obj-c wrapper for sqlite3 that works in Leopard, please let us know. If I had some code that works to look at, I should be able to adapt it for macruby. framework 'QuickLite.framework' # fails with the error below framework 'QuickLite' # fails can't find file Error Domain=NSCocoaErrorDomain Code=3585 UserInfo=0x800621ae0 "The bundle “QuickLite” could not be loaded because it does not contain a version for the current architecture." On Tue, Mar 31, 2009 at 7:24 AM, wrote: > Send MacRuby-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. Re: Can any kind macruby experts help me get sqlite3 gem > working with macruby--please? (Matt Aimonetti) > > > -- > > Message: 1 > Date: Tue, 31 Mar 2009 01:51:07 -0700 > From: Matt Aimonetti > Subject: Re: [MacRuby-devel] Can any kind macruby experts help me get > sqlite3 gem working with macruby--please? > To: "MacRuby development discussions." > > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="utf-8" > > the sqlite3 gem uses a native C extension which needs to compiled for your > system. (usually done when installed via rubygems) > The installation will fail if you use macgem, probably due to some IO issues > and the lack of support of C extension. > > Someone should look into writing a wrapper for macruby using an obj-c > driver. That can't be that hard and that would be very useful. I've been > thinking about porting the DataObject and the DO SQlite3 driver to MacRuby > but I didn't have time yet (and I didn't really need it either). DataObject > is the uniform API used by DataMapper to talk to its drivers. > If someone is interested in working on that, I can put him/her in contact > with the DM team. > > - Matt > > > > 2009/3/31 Tim Rand > >> Can any kind macruby experts help me get sqlite3 gem working with macruby? >> >> sqlite3-ruby-1.2.4 ruby gem works in ruby 1.9.0. So I think it should work >> in macruby also... >> From macirb I added the path to the gem: >> >> $: << "path/to/the/sqlite3-ruby-1.2.4/lib" >> >> require 'sqlite3.rb' # => true >> >> $db = SQLite3::Database.new("/path/to/x.db.rsd") >> >> RuntimeError: *no driver for sqlite3 found* >> the error comes from the load_driver method near line 621 of the >> sqlite3/database.rb file. >> >> def load_driver( driver ) >> case driver >> when Class >> # do nothing--use what was given >> when Symbol, String >> require "sqlite3/driver/#{driver.to_s.downcase}/driver" >> driver = SQLite3::Driver.const_get( driver )::Driver >> else >> [ "Native", "DL" ].each do |d| >> begin >> require "sqlite3/driver/#{d.downcase}/driver" >> driver = SQLite3::Driver.const_get( d )::Driver >> break >> rescue SyntaxError >> raise >> rescue ScriptError, Exception, NameError >> end >> end >> raise "no driver for sqlite3 found" unless driver >> end >> >> @driver = driver.new >> end >> private :load_driver >> >
[MacRuby-devel] macruby and sqlite3 gem
Hi Jordon, Thanks for the idea. I tried it (arch -arch i386 macirb), but get the same error. Tim Jordon suggested: "does not contain a version for the current architecture" sounds like a 32-bit vs. 64-bit problem to me. MacRuby 0.4 has both i386 and x86_64 archs for macruby and macirb, on a capable system it will pick the x86_64 arch first, which means any frameworks you load while running that arch need to have x86_64 in their Framework/library/bundle as well. What happens if you try running with something like `arch -arch i386 macruby` or `arch -arch i386 macirb` instead? ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] Tim added you as a friend on MyLife!
Tim Rand added you as a friend on MyLife(TM). Please confirm you know Tim so we can connect you. Do You Know Tim? YES - Connect with Tim, and see who's searching for you http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&[email protected]&userid=251423&extra=&&&2002&&&http://www.mylife.com/showInviteRegistration.do?uid=357900586&[email protected] NO - I don't know Tim http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&[email protected]&userid=251423&extra=&&&2000&&&http://www.mylife.com/showInviteRegistration.do?unsub=true&[email protected]&uid=357900586 ~~ MyLife - Find everyone. All in one place.(TM) You have received this email because a MyLife member sent an invitation to this email address. For assistance, please refer to our FAQ or Contact Us: http://smtp26.mail.reunion.com:80/track?type=click&mailingid=68900&messageid=9300&databaseid=1238061926&serial=1228209694&[email protected]&userid=251423&extra=&&&2001&&&http://help.mylife.com/ Our Address: 2118 Wilshire Blvd., Box 1008, Santa Monica, CA 90403-5784 Copyright (c) 2009 MyLife.com, Inc. All Rights Reserved. ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] question about goals for ruby module compatibility with macruby
Hi Laurent and macruby-ists,I am thinking about taking on a rather ambitious project with macruby in the next year or so which would benefit from having access to existing ruby gems (like the bioruby gem and rails). Can anyone predict how general the ruby gem compatibility will be as macruby matures? I promise I won't hold anyone responsible for their speculation. Tim ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] has anyone else noticed hotcocoa/graphics is no longer working...
Though the following code works on macruby 0.4 and mac OS 10.5.8, it no longer works for me since updating macruby and the OS: macruby -e 'require "hotcocoa/graphics"' -e:1:in `': private method `define_method' called for Class:Class (NoMethodError) I am running: OS 10.6.2 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64] (with ruby version 1.9.0) I don't see a define_method call anywhere in the source code in the /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/hotcocoa/graphics.rb file. I just want to tinker with HotCocoa::Graphics. Any advice or explanation would be appreciated. Thanks, Tim ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] has anyone else noticed hotcocoa/graphics is no longer working..
I am running 0.5 beta2 not the latest development trunk. I'll try updating. I believe I fixed this bug after 0.5 beta2, what version are you on? > > - Matt > > On Wed, Dec 2, 2009 at 3:51 PM, Tim Rand wrote: > > > Though the following code works on macruby 0.4 and mac OS 10.5.8, it no > > longer works for me since updating macruby and the OS: > > > > macruby -e 'require "hotcocoa/graphics"' > > -e:1:in `': private method `define_method' called for Class:Class > > (NoMethodError) > > > > I am running: > > OS 10.6.2 > > MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64] > > (with ruby version 1.9.0) > > > > I don't see a define_method call anywhere in the source code in the > > > /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/hotcocoa/graphics.rb > > file. > > > > I just want to tinker with HotCocoa::Graphics. > > Any advice or explanation would be appreciated. > > > > Thanks, > > Tim > > > > ___ > > MacRuby-devel mailing list > > [email protected] > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091202/7345279f/attachment-0001.html > > > > -- > > Message: 5 > Date: Thu, 03 Dec 2009 01:10:55 - > From: "MacRuby" > To: undisclosed-recipients:; > Cc: [email protected] > Subject: [MacRuby-devel] [MacRuby] #475: GCD Queues should print their >label as their "to_s" method > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > #475: GCD Queues should print their label as their "to_s" method > > +--- > Reporter: ernest.prabha...@? | Owner: lsansone...@? > Type: enhancement | Status: new > Priority: blocker | Milestone: MacRuby 0.5 > Component: MacRuby |Keywords: > > +--- > Right no, GCD Queues have a generic (i.e., mostly useless) "to_s" method. > Why not just make the GCD "label" method act as to_s: > > http://github.com/masterkain/macruby/blob/master/gcd.c > > rb_objc_define_method(cQueue, "to_s", rb_queue_label, 0); > > That avoids additional API, and lets it generally "do the right thing" > > -- > Ticket URL: <http://www.macruby.org/trac/ticket/475> > MacRuby <http://macruby.org/> > > > > -- > > Message: 6 > Date: Thu, 03 Dec 2009 01:37:26 - > From: "MacRuby" > To: undisclosed-recipients:; > Cc: [email protected] > Subject: [MacRuby-devel] [MacRuby] #476: GCD Groups should be a >wrapper around dispatch, not its own invocation style > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > #476: GCD Groups should be a wrapper around dispatch, not its own > invocation > style > > +--- > Reporter: ernest.prabha...@? | Owner: lsansone...@? > Type: enhancement | Status: new > Priority: blocker | Milestone: MacRuby 0.5 > Component: MacRuby |Keywords: gcd > > +--- > Right now, GCD Groups are treated almost like a Queue, so developers call > dispatch on them -- except that: > - you need to specify a queue as a parameter -- or use (atypically) have > it invisibly invoke the default queue > - there's no way to specify synchronous dispatch > > This works well if you really just want async concurrency, but becomes > awkward (and IMHO confusing) for anything else. > > g = Dispatch::Group.new > g.dispatch {work_function(i)}} > g.dispatch(q_a) {work_function(i)}} > g.dispatch(q_b, false) {work_function(i)}} > g.wait > > I don't know if it is possible, but what I'd prefer is for Groups to take > a block *containing* multiple dispatch invocations, and auto-magically > associate them with a group. > >
[MacRuby-devel] mac & ruby question
I am sorry. This is not a macruby question per se, just a question about plain old ruby on mac (specifically snow leopard) question. But you guys for sure will know the answer, so I must ask. Why is it that after upgrading to snow leopard (10.6.2) a long list of gems no longer run on ruby 1.9.1? Using Matt Aimonetti's sl_gems_update.rb file, I get: Please reinstall: eventmachine versions: 0.12.0, 0.12.0 fastthread versions: 1.0.1, 1.0.1 hpricot versions: 0.6.161, 0.6.161, 0.8.2, 0.8.2, 0.8.2, 0.8.2 hpricot-0.6.161/lib/universal versions: darwin9.0, darwin9.0 mongrel versions: 1.1.5, 1.1.5 rb-appscript versions: 0.5.1, 0.5.1 rmagick versions: 2.2.0, 2.2.0 rsruby versions: 0.4.5, 0.4.5 ruby-debug-base versions: 0.10.3, 0.10.3 sqlite3-ruby versions: 1.2.1, 1.2.1 tioga versions: 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8 tmail versions: 1.2.3.1, 1.2.3.1 Indeed, I had noticed already that hpricot, rsruby, and sqlite3 were no longer working. Reinstalling eventmachine and fastthread worked. But many of the others appear to install, but don't function: Tim:~/Desktop/RubyClub> sudo env ARCHFLAGS="-arch i386" gem install why-hpricot --source http://gems.github.com Building native extensions. This could take a while... Successfully installed why-hpricot-0.7.229 1 gem installed Installing ri documentation for why-hpricot-0.7.229... Installing RDoc documentation for why-hpricot-0.7.229... Tim:~/Desktop/RubyClub> gem which hpricot (checking gem why-hpricot-0.7.229 for hpricot) /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot.rb Tim:~/Desktop/RubyClub> ruby -e 'require "hpricot"' /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot.rb:20:in `require': dlopen(/usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot_scan.bundle, 9): no suitable image found. Did find: (LoadError) /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot_scan.bundle: mach-o, but wrong architecture - /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot_scan.bundle from /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot.rb:20:in `' from -e:1:in `require' from -e:1:in `' And file on that path gives: file /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot_scan .bundle Mach-O 64-bit bundle x86_64 I am pretty sure that the problem is with .bundle files being compiled for x86_64 architecture, but I explicitly told the os to use env ARCHFLAGS="-arch i386" and it ignored it and put the bundle files in the x86_64 architecture anyhow. I am stuck. Why am I getting the mach-o but wrong architecture error? It seems to be a problem with gems that have .bundle files. If anyone can explain how I should be installing gems in snow leopard so that they actually work, I would really like that person. Seriously. Tim ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] mac & ruby question
Hi Conrad, You are totally right--if I make 1.8.7 the default ruby version I can install and run rsruby gem without a hitch. Same install on 1.9.1 doesn't work. I investigated and as suspected the 1.8.7 gem install provides both the i386 binary and the x86_64 binary files while the 1.9.1 gem install only creates the x86_64 binary (see below). I'm still puzzled by what is influencing which type of file is generated--it doesn't seem to listen to the command line as sudo ARCHFLAGS="-arch i386" gem install rsruby -- --with-R-dir=$R_HOME wouldn't force the i386 binary to be produced. Don't you think this behavior is weird? Is it the placement within the file system that makes the OS decide whether this or that type of binary should be generated? And how do I force 1.9.1 gem install to do what 1.8.7 gem install does? Tim:~/.gem/ruby/1.8/gems/rsruby-0.5.1.1/lib> ls rsruby rsruby.rb rsruby_c.bundle Tim:~/.gem/ruby/1.8/gems/rsruby-0.5.1.1/lib> file rsruby_c.bundle rsruby_c.bundle: Mach-O universal binary with 2 architectures rsruby_c.bundle (for architecture i386): Mach-O bundle i386 rsruby_c.bundle (for architecture x86_64): Mach-O 64-bit bundle x86_64 Tim:~/.gem/ruby/1.8/gems/rsruby-0.5.1.1/lib> gem19 which rsruby (checking gem rsruby-0.5.1.1 for rsruby) /usr/local/lib/ruby19/gems/1.9.1/gems/rsruby-0.5.1.1/lib/rsruby.rb Tim:~/.gem/ruby/1.8/gems/rsruby-0.5.1.1/lib> cd /usr/local/lib/ruby19/gems/1.9.1/gems/rsruby-0.5.1.1/lib Tim:/usr/local/lib/ruby19/gems/1.9.1/gems/rsruby-0.5.1.1/lib> ls rsruby rsruby.rb rsruby_c.bundle Tim:/usr/local/lib/ruby19/gems/1.9.1/gems/rsruby-0.5.1.1/lib> file rsruby_c.bundle rsruby_c.bundle: Mach-O 64-bit bundle x86_64 On Mon, Dec 7, 2009 at 7:00 AM, wrote: > Send MacRuby-devel mailing list submissions to >[email protected] > > To subscribe or unsubscribe via the World Wide Web, visit >http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > or, via email, send a message with subject or body 'help' to >[email protected] > > You can reach the person managing the list at >[email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. Re: mac & ruby question (Conrad Taylor) > 2. Re: UTF8 Strings [resolved] (s.ross) > > > -- > > Message: 1 > Date: Sun, 6 Dec 2009 21:22:46 -0800 > From: Conrad Taylor > To: "MacRuby development discussions." > > Subject: Re: [MacRuby-devel] mac & ruby question > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii"; Format="flowed"; >DelSp="yes" > > TIm, does gems install correctly with Ruby 1.8.7 which is the default > in Snow Leopard? This should be the case. Next, x86_64 is the > default under Snow Leopard and your bundles are being correctly. > Thus, I would recommend sticking with default compilation settings. > For example, the following is all you need: > > gem install hpricot > > Thus, I would recommend going through the process again of reinstalling. > > Good luck, > > -Conrad > > Sent from my iPhone > > On Dec 6, 2009, at 8:43 PM, Tim Rand wrote: > > > I am sorry. This is not a macruby question per se, just a question > > about plain old ruby on mac (specifically snow leopard) question. > > But you guys for sure will know the answer, so I must ask. Why is it > > that after upgrading to snow leopard (10.6.2) a long list of gems no > > longer run on ruby 1.9.1? > > > > Using Matt Aimonetti's sl_gems_update.rb file, I get: > > Please reinstall: > > eventmachine versions: 0.12.0, 0.12.0 > > fastthread versions: 1.0.1, 1.0.1 > > hpricot versions: 0.6.161, 0.6.161, 0.8.2, 0.8.2, 0.8.2, 0.8.2 > > hpricot-0.6.161/lib/universal versions: darwin9.0, darwin9.0 > > mongrel versions: 1.1.5, 1.1.5 > > rb-appscript versions: 0.5.1, 0.5.1 > > rmagick versions: 2.2.0, 2.2.0 > > rsruby versions: 0.4.5, 0.4.5 > > ruby-debug-base versions: 0.10.3, 0.10.3 > > sqlite3-ruby versions: 1.2.1, 1.2.1 > > tioga versions: 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8 > > tmail versions: 1.2.3.1, 1.2.3.1 > > > > Indeed, I had noticed already that hpricot, rsruby, and sqlite3 were > > no longer working. > > Reinstalling eventmachine and fastthread worked. > > But many of the others appear to install, but don't function: > > > > Tim:~/Deskt
[MacRuby-devel] obj.method(m) often gives a TypeError
I noticed that obj.method(m) is often giving an error. The error given on [].methods looks like: Tim:~/Desktop> macirb >> def err(obj) >> obj.methods(1,1).each do |m| ?> begin ?> obj.method(m) >> rescue => e >> p e >> end >> end >> end => nil >> err([]) # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # No errors are raised with the same code (without parameters on the methods of course) in ruby 1.9.1. ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
[MacRuby-devel] Re The Future of MacRuby
I am surprised to hear Laurent has left Apple. I don't know what motivated the change, but I am sure that he is working on something great. Good luck Laurent!!! While I have a lot of faith in the open source community and think growing a larger pool of contributors is critical for the long-term viability of macruby, the libauto issue is a simple example of how internal decisions at Apple can have profound effects on macruby's future. That worries me. Without anyone promoting macruby from inside Apple, they can shut compatibility with x-code off with an update, add months of work to remove libauto-dependency because they decide to deprecate GC or otherwise alter the programming universe in some unforeseen way. Since Apple is an unapologetic, iron-curtain of secrecy, with a propensity to stop short and change direction (remember when it seemed like macruby would be on iOS?), I can only imagine how many hacker years the macruby community will burn while trying to hit an ever-moving target. Apple, think different--don't be evil! --Tim On Thu, Apr 5, 2012 at 9:02 PM, wrote: > Send MacRuby-devel mailing list submissions to >[email protected] > > To subscribe or unsubscribe via the World Wide Web, visit >http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > or, via email, send a message with subject or body 'help' to >[email protected] > > You can reach the person managing the list at >[email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > > 1. Re: Re The Future of MacRuby (Jordan K. Hubbard) > 2. Re: The future of MacRuby (Chong Francis) > > > -- > > Message: 1 > Date: Thu, 05 Apr 2012 17:45:48 -0700 > From: "Jordan K. Hubbard" > To: "MacRuby development discussions." > > Subject: Re: [MacRuby-devel] Re The Future of MacRuby > Message-ID: > Content-Type: text/plain; charset="us-ascii" > > > On Apr 5, 2012, at 3:34 PM, Dan Farrand > wrote: > > > I am not a a contributor to MacRuby, but I have been interested in using > it. Without Apple sponsorship, I have very little interest in MacRuby. > > I think Matt has already said all that needs to be said on that subject. > There are many application environments, both commercial (like Unity3D) > and open source (like Mono), that have enjoyed a healthy and robust > existence without Apple's help. Apple is a wonderful company that makes > many fine things (and I'm obviously biased), but it would be frankly silly > to suggest or even imagine that no one else is capable of making fine > things on their own. One also need look no further than the MacPorts > project to see one that was started by Apple but became FAR more successful > and motivated once the community became seriously involved with and took > over the development process, so there's a counter-point to your somewhat > pessimistic viewpoint right there. > > I personally wish Matt and anyone who wishes to join him in charting > MacRuby's future course the very best of luck. As he notes, it's already a > fairly stable platform and a lot of good work has already gone into it: > It's hardly starting from scratch with just a few gossamer dreams and > ill-defined notions to hang its future on! You have some great stuff to > start with. > > Even better, it's open source and the doors are therefore open to anyone > who wishes to participate. No hosting situation is perfect, of course, and > should there be any impediments to such participation then I'm sure they > will rapidly resolve themselves given the plethora of alternatives for > hosting the bits, the bug reports, the community discussion portals, and so > on. Those are mere implementation details, however, and it's far more > important that the project have some clearly defined goals and people > willing to drive those goals since, as I can personally attest, the heart > and soul of any open source project is the people involved with it on a day > to day basis! Not the source code. Not where the sources are hosted. The > people. > > There simply has to be some collection of people who constitute an actual > community since it is communities, and the essential need that humans have > for creating them, that binds any project together and leads to its > longer-term success. Individuals themselves may come and go, just as I > left the FreeBSD project after many years of involvement with it, but as > long as there is a strong community of like-minded individuals remaining > then the project will live on and continue to prosper (I like to think that > FreeBSD is far more successful today than it was when I left it). > Focusing on the past merely leads to pointless navel-gazing. Think about > the future you want to create, as Matt says, and you'll be on the
Re: [MacRuby-devel] Update (Laurent Sansonetti)
"First, we will release master as 0.12 (and just forget about 0.11). It is important since master has changes for the latest Xcode that have never been snipped yet." Does that mean the macruby project template will be updated to work with xcode 4.3.2--i.e. install into the updated directory location (/Applications/Xcode.app/Contents/Developer/Library/Xcode/Templates/Project\ Templates/Mac/Application/) and have a .xctemplate structure? Because I was just trying (but failing) to get figure out how to access the templates from the xcode 4.3.2. Moving the old templates (from /Library/Application\ Support/Developer/Shared/Xcode/Project\ Templates/Application/) didn't work. Looks like lots of stuff changed regarding xcode templates with this update. Thanks, Tim ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] MacRuby-devel Digest, Vol 66, Issue 1
There was some mention in the most resent rubymotion release notes that rubymotion was now capable of writing Mavericks os X Apps (including eval() ). So there is a solution. I am not sure Laurent will be willing to share the solution back to macruby though. Tim On Sat, Nov 2, 2013 at 7:44 PM, wrote: > Send MacRuby-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.macosforge.org/mailman/listinfo/macruby-devel > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of MacRuby-devel digest..." > > > Today's Topics: > >1. Mavericks and Macruby (rob ista) >2. Re: Mavericks and Macruby (Steve Clarke) >3. Re: Mavericks and Macruby (Joshua Ballanco) >4. Re: Mavericks and Macruby (Robert Carl Rice) >5. Re: Mavericks and Macruby (Andres Santos) > > > -- > > Message: 1 > Date: Sat, 02 Nov 2013 20:02:59 +0100 > From: rob ista > To: [email protected] > Subject: [MacRuby-devel] Mavericks and Macruby > Message-ID: > Content-Type: text/plain; charset="windows-1252" > > Something seems to be broken since the upgrade to Mavericks. Macgems don?t > want to load anymore: > > Robs-iMac:~ rob$ macgem list > /usr/local/bin/macgem:9:in `': undefined method `summary_indent=' > for class `OptionParser' (NameError) > > This is just an example. A ?require macgems? followed by e.g. ?require > uri? results in similar errors. > > Anyone any clue? > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.macosforge.org/pipermail/macruby-devel/attachments/20131102/13239b5b/attachment-0001.html > > > > -- > > Message: 2 > Date: Sat, 2 Nov 2013 23:06:56 + > From: Steve Clarke > To: "MacRuby development discussions." > > Subject: Re: [MacRuby-devel] Mavericks and Macruby > Message-ID: > Content-Type: text/plain; charset="windows-1252" > > I've had that and other problems too. > > The standard library 'set' no longer works, though it's fairly easy to > substitute NSMutableSet. I can't run one of my main apps on Mavericks. > > Is this the beginning of the end or even the end of the end for Macruby? > > On 2 Nov 2013, at 19:02, rob ista wrote: > > > Something seems to be broken since the upgrade to Mavericks. Macgems > don?t want to load anymore: > > > > Robs-iMac:~ rob$ macgem list > > /usr/local/bin/macgem:9:in `': undefined method `summary_indent=' > for class `OptionParser' (NameError) > > > > This is just an example. A ?require macgems? followed by e.g. ?require > uri? results in similar errors. > > > > Anyone any clue? > > ___ > > MacRuby-devel mailing list > > [email protected] > > https://lists.macosforge.org/mailman/listinfo/macruby-devel > > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.macosforge.org/pipermail/macruby-devel/attachments/20131102/a8923661/attachment-0001.html > > > > -- > > Message: 3 > Date: Sun, 3 Nov 2013 02:32:15 +0200 > From: Joshua Ballanco > To: "MacRuby development discussions." > > Subject: Re: [MacRuby-devel] Mavericks and Macruby > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > I haven't had time to update to Mavericks yet, so I couldn't tell you for > sure, but the "summary_indent=" error looks like it may be a consequence of > the upgraded 2.0 version of Ruby on the system. IIRC, there should still be > a copy of the 1.8 Ruby version (under /System/Library I think?). If you > change the #! line in "macgem" to point specifically to Ruby 1.8, things > may start working again? > > > > On Sunday, November 3, 2013 at 1:06 AM, Steve Clarke wrote: > > > I've had that and other problems too. > > > > The standard library 'set' no longer works, though it's fairly easy to > substitute NSMutableSet. I can't run one of my main apps on Mavericks. > > > > Is this the beginning of the end or even the end of the end for Macruby? > > > > On 2 Nov 2013, at 19:02, rob ista [email protected])> wrote: > > > Something seems to be broken since the upgrade to Mavericks. Macgems > don?t want to load anymore: > > > > > > Robs-iMac:~ rob$ macgem list > > > /usr/local/bin/macgem:9:in `': undefined method > `summary_indent=' for class `OptionParser' (NameError) > > > > > > > > > This is just an example. A ?require macgems? followed by e.g. ?require > uri? results in similar errors. > > > > > > Anyone any clue? ___ > > > MacRuby
