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

[MacRuby] #363: IO.copy_stream dont handle copyfile.
by MacRuby 04 Oct '09

04 Oct '09

#363: IO.copy_stream dont handle copyfile. --------------------------------+------------------------------------------- Reporter: kazuhisa@… | Owner: lsansonetti@… Type: defect | Status: new Priority: minor | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: --------------------------------+------------------------------------------- I try to run folloing script. {{{ src = open("a") dst = open("b","w+") IO.copy_stream(src,dst) src.close dst.close }}} I expected to run via copyfile function . but not. because src/dst object is indicated as not T_FILE by rb_type.(T_NATIVE) -- Ticket URL: <http://www.macruby.org/trac/ticket/363> MacRuby <http://macruby.org/>

1 2

Supported classes & methods diagram fed from rubyspec
by Ben Schwarz 03 Oct '09

03 Oct '09

Hi all, I've had some loose discussions with @lrz regarding a visual representation of classes and methods that are working via the rubyspec. This would enable developers to find an area of development to focus on and also for end-users to understand what they might face before conducting any development using macruby (bringing real applications closer to tuition, rather than a start/stop experience) I'm happy to offer some hours to get something together that is styled like macruby.org but I obviously need to: A) consult the group B) work out a spec C) have something setup on the macruby.org infrastructure. Discuss. Cheers, - Ben Schwarz Web architect Web: http://www.germanforblack.com Mobile: +61 407 339 418 -- Please consider your environment before printing or distributing this material. --

5 9

Xcode Project Template with Testing Baked In
by Dylan Bruzenak 02 Oct '09

02 Oct '09

So, I've been mucking about with MacRuby lately. It's been fun so far. Thanks to all the devs for this great project. I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby on Rails and similar frameworks nudge you in the right direction by baking in an existing testing infrastructure. I've got testing pretty much figured out and was wondering if the team would be open to modifying the basic Xcode project template to add unit testing, with a stub test and test_suite file to get started. This would also involve creating a framework for any objective-c code that the user writes so that it can be included in both the .app and the test files. In addition it might be useful to include the 'embed mac ruby' and possibly a macrubyc target as well by default. These can always be removed if a user doesn't want them. I can supply preliminary patches if this seems like a good route to go. - Dylan Bruzenak www.ideaswarm.com

3 11

How to compile all ruby files in a project using macrubyc
by Dylan Bruzenak 02 Oct '09

02 Oct '09

I'm a bit of a newbie when it comes to command line compilation. Is there an easy way for me to basically just say: compile everything recursively, starting at this directory ? Given that, what would be the best way to then integrate that with an Xcode project as part of a target ? Also, is this far enough along to consider adding to the project templates by default ? thanks! - Dylan

3 6

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In
by Dylan Bruzenak 02 Oct '09

02 Oct '09

Message is being held pending moderator approval; let me know if I should post the actual file somewhere else :) - Dylan On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan(a)ideaswarm.com> wrote: > Good idea. I've attached it here. I may have accidentally added the build > directory as well; this should be deleted from the template. > > To test you can copy it to one of the template directories such as : > ~/Library/Application Support/Developer/Shared/Xcode/Project > Templates/Application/MacRuby Application With Testing > > Differences: > > - Embed MacRuby target is included by default to easy deployment for first > time users > - Tests directory has been added for tests > - test_stub.rb has been added with a starting test::unit case > - Unit Tests target has been added to run the tests > - test_suite.rb has been added to load up all tests from the Tests > directory. This can easily be made recursive using Dir.glob. > > I've left out the framework/obj-c testing stuff because it is difficult to > get it working in cases where there is no objective-c; building the > framework requires at least one class. A better way to handle that would be > to write up a blog post on how to do this; mainly: > > 1.) Create a new Cocoa -> Framework target > 2.) add the new framework to your unit test and .app targets so that it > gets built when either target is run > 3.) add a copy files step, targeting frameworks, to your .app target > 4.) add the new framework(drag from the products folder) to both the link > and copy steps of your .app target to include it with your .app file > 5.) add "framework 'newframeworkname'" to your rb_main.rb file > 6.) add "framework 'build/Debug/newframeworkname.framework' to your > test_suite.rb file > > After following these steps you can test any Obj-c classes added to the > framework from Ruby, as well as any Ruby classes that depend on these custom > classes. > > - Dylan > > > On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti(a)gmail.com>wrote: > >> Hi Dylan, >> >> Why don't you you post your template so people can look at it and give >> their feedback? People like Eloy would probably give their feedback ;) >> >> - Matt >> >> >> >> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan(a)ideaswarm.com>wrote: >> >>> So, I've been mucking about with MacRuby lately. It's been fun so far. >>> Thanks to all the devs for this great project. >>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby >>> on Rails and similar frameworks nudge you in the right direction by baking >>> in an existing testing infrastructure. >>> >>> I've got testing pretty much figured out and was wondering if the team >>> would be open to modifying the basic Xcode project template to add unit >>> testing, with a stub test and test_suite file to get started. This would >>> also involve creating a framework for any objective-c code that the user >>> writes so that it can be included in both the .app and the test files. >>> >>> In addition it might be useful to include the 'embed mac ruby' and >>> possibly a macrubyc target as well by default. These can always be removed >>> if a user doesn't want them. >>> >>> I can supply preliminary patches if this seems like a good route to go. >>> >>> - Dylan Bruzenak >>> www.ideaswarm.com >>> >>> >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel(a)lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel(a)lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> >

4 6

Objective-C SDL bindings accessible from Ruby?
by Timothy McDowell 01 Oct '09

01 Oct '09

I'm fairly new to objective-c, xcode, and the whole compiling/linking process altogether. But I was wondering if I link my SDL library to my xcode macruby project, can I access the SDL from both the Obj-C side and Ruby? -- --Timothy.

2 3

[MacRuby] #357: NSLog causes "BAD_EAX_ACCESS" on 10.6
by MacRuby 01 Oct '09

01 Oct '09

#357: NSLog causes "BAD_EAX_ACCESS" on 10.6 ------------------------------------------+--------------------------------- Reporter: mitchell.hashimoto@… | Owner: lsansonetti@… Type: defect | Status: new Priority: blocker | Milestone: Component: MacRuby | Keywords: ------------------------------------------+--------------------------------- I simply added an NSLog to rb_main.rb prior to NSApplicationMain to attempt to log some dummy data ("Foo") and it crashes with BAD_EAX_ACCESS everytime. When I remove that line, it runs fine. This is on 10.6 Snow Leopard with the latest head (commit e3c2cbc6bac26594d3a722cfcc652cad11fcd524 in git-svn). {{{ # Loading the Cocoa framework. If you need to load more frameworks, you can # do that here too. framework 'Cocoa' # Loading all the Ruby project files. dir_path = NSBundle.mainBundle.resourcePath.fileSystemRepresentation Dir.entries(dir_path).each do |path| if path != File.basename(__FILE__) and path[-3..-1] == '.rb' require(path) end end # Test Log, should crash program NSLog "Foo Bar Baz" # Starting the Cocoa main loop. NSApplicationMain(0, nil) }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/357> MacRuby <http://macruby.org/>

1 2

[MacRuby] #306: NSPredicate.predicateWithFormat crashes with Segmentation fault
by MacRuby 01 Oct '09

01 Oct '09

#306: NSPredicate.predicateWithFormat crashes with Segmentation fault ------------------------+--------------------------------------------------- Reporter: dev@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: MacRuby 0.5 Component: MacRuby | Keywords: NSPredicate ------------------------+--------------------------------------------------- {{{ macruby -e "framework 'Cocoa'; p NSPredicate.predicateWithFormat(%q/a == 'b'/)" }}} causes (in most of the cases) the following result: {{{ unknown: [BUG] Segmentation fault MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, x86_64] Abort trap }}} In some rare cases it works: {{{ #<NSComparisonPredicate:0x80030c440> }}} -- Ticket URL: <http://www.macruby.org/trac/ticket/306> MacRuby <http://macruby.org/>

1 2