If someone wants to try to run rspec 2.0 alpha, that would be cool. (code available on github) - Matt On Sun, Nov 22, 2009 at 5:15 PM, Laurent Sansonetti <lsansonetti@apple.com>wrote:

Hi Giampiero,

The latest 0.5 beta doesn't run rspec, AFAIK. The rspec code is using too much dark magic that MacRuby can actually handle. Last time we check, we fail to run it because our #caller returns something different than the original Ruby.

We might eventually run rspec in the next beta. I heard they are cleaning the code at the moment so maybe we will run it, indirectly.

I know nothing about Cucumber support, yet. As usual, if you want to help, please try it, if it doesn't work, investigate why, reduce the problem and file a Trac report :-)

Laurent

On Nov 21, 2009, at 12:17 PM, Giampiero De Ciantis wrote:

I know the topic of RSpec support has come up before, specifically about

...

why it doesn't function. Does anyone know if the fixes in the 0.5 release will cover those issues? Or is this something of 0.6?

Cheers,

-Gp _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

On Sun, Nov 22, 2009 at 10:08 PM, Joshua Ballanco <joshua.ballanco@apple.com

wrote:

I've been playing with Cucumber, but so far there are still a few issues. It doesn't seem like anything quite so hard to deal with as RSpec, but it's still early days.

- Josh

Josh, do you mean you're seeing issues with Cucumber on MacRuby? In any case, the one good thing good about gemcutter.org is that they display the runtime dependencies if any for a given gem. At this time, the cucumber gem has the following runtime dependencies: *erm-ansicolor <http://www.gemcutter.org/gems/term-ansicolor>* = 1.0.4<http://www.gemcutter.org/gems/term-ansicolor> <http://www.gemcutter.org/gems/term-ansicolor>*treetop* = 1.4.2<http://www.gemcutter.org/gems/treetop> <http://www.gemcutter.org/gems/treetop>*polyglot* = 0.2.9<http://www.gemcutter.org/gems/polyglot> <http://www.gemcutter.org/gems/polyglot>*builder* = 2.1.2<http://www.gemcutter.org/gems/builder> <http://www.gemcutter.org/gems/builder>*diff-lcs* = 1.1.2<http://www.gemcutter.org/gems/diff-lcs> In addition to the above list, a lot of people tend to use the webrat gem as well when using cucumber. Anyway, I looked the RSpec and it was out of my level of expertise. RSpec team also said that they were in the process of cleaning up things to make it easier to run on the various VMs. In the meantime, I'll see what happens with RSpec 2.0 alpha and MacRuby. -Conrad

On Nov 22, 2009, at 8:15 PM, Laurent Sansonetti wrote:

...

Hi Giampiero,

The latest 0.5 beta doesn't run rspec, AFAIK. The rspec code is using too much dark magic that MacRuby can actually handle. Last time we check, we fail to run it because our #caller returns something different than the original Ruby.

We might eventually run rspec in the next beta. I heard they are cleaning the code at the moment so maybe we will run it, indirectly.

I know nothing about Cucumber support, yet. As usual, if you want to help, please try it, if it doesn't work, investigate why, reduce the problem and file a Trac report :-)

Laurent

On Nov 21, 2009, at 12:17 PM, Giampiero De Ciantis wrote:

...

I know the topic of RSpec support has come up before, specifically about why it doesn't function. Does anyone know if the fixes in the 0.5 release will cover those issues? Or is this something of 0.6?

Cheers,

-Gp _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Without testing tools I think you are asking for trouble. That's what keeps me waiting. I would also wait for Apple to support it as a product. But I would confident if I had the appropriate safety net in testing tools. Cheers, -Gp On 2009-11-23, at 4:27 PM, Matthew Winter wrote:

Hi,

I was wondering if anyone thinks or has plans to use MacRuby 0.5 for a commercial application.

My opinion is that with enough testing and waiting for the final 0.5 release that it would be good enough. Especially if the app can auto update so newer releases of MacRuby could be embedded.

What does the group think to this?

Regards Matthew Winter _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Cucumber and RSpec are the tools I am familiar with. I know Bacon is an Rspec clone, but it doesn't handle some relatively simple applications I have built using RSpec. So it isn't going to work for me. If you are a Cocoa developer moving to MacRuby, maybe the tools available suffice. The lack of RSpec and Cucumber support is a showstopper for me. -Gp On 2009-11-23, at 4:38 PM, Matt Aimonetti wrote:

What kind of testing tools are you thinking of? You can use Bacon to test your code, I believe Josh posted an example on the macruby website.

I personnaly think that you can start your production application now and embed 0.5/trunk with the final release.

Good luck

-Matt

Sent from my iPhone

On Nov 23, 2009, at 13:29, Giampiero De Ciantis <gdeciantis@gmail.com> wrote:

...

Without testing tools I think you are asking for trouble. That's what keeps me waiting. I would also wait for Apple to support it as a product. But I would confident if I had the appropriate safety net in testing tools.

Cheers,

-Gp

On 2009-11-23, at 4:27 PM, Matthew Winter wrote:

...

Hi,

I was wondering if anyone thinks or has plans to use MacRuby 0.5 for a commercial application.

My opinion is that with enough testing and waiting for the final 0.5 release that it would be good enough. Especially if the app can auto update so newer releases of MacRuby could be embedded.

What does the group think to this?

Regards Matthew Winter _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

---

MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

I am not sure, maybe I am doing something wrong, but here is what I have tried: 1. Use RVM to make MacRuby my default Ruby 2. Install the Cucumber gem while MacRuby is my default VM 3. Run cucumber on an existing Ruby app that is tested using Cucumber (This fails every time I have tried) 4. Run RSpec on the same Ruby app (This also fails every time I have tried) 5. Add Cucumber features that describe the GUI 6. Build out the GUI I realize that 5 and 6 would require me to build some kind of other tool like webrat (Cocoarat?), but that brings me to my next idea. The project I have wanted to start for a while was to build something equivalent to Merb or Rails for Cocoa applications. Something that allows you to avoid XCode altogether and sets you up with the right frameworks and plugins to get a lot done fast. But a framework of this kind can get nasty quick if you don't have some kind of testing harness. Further, Ruby is a terrible language without testing tools. It gives you way more opportunities to screw stuff up if you don't have some kind of safety net. I hope that helps you understand where I am coming from. I am a big supporter of BDD since, as a product manager, it helps me get the most out of the work that me and the team do to build software products. How I got here is a story that requires many beers, my treat. Cheers, -Gp On 2009-11-23, at 5:49 PM, Matt Aimonetti wrote:

I see, out of curiosity, how would you expect cucumber to work for a cocoa app?

- Matt

Sent from my iPhone

Hi Matthiew, If you are considering using MacRuby to build a commercial Cocoa app, you should also consider the following limitations: - Limited Ruby compatibility. Our compatibility is not bad but if you want to use 3rd party Ruby libraries or gems you may hit some bugs. We are actively fixing these bugs as they are reported, but you need to be willing to report them and be patient. - No support for C extensions. If you want to use a native gem, it will not work. - No debugger (in Xcode). - No support to build an app that works on both Leopard and Snow Leopard. We are working to address these limitations in the next (0.6) release. On the other side, we have fairly stable Cocoa support. If you are using pure Cocoa APIs in your app, MacRuby should today be an excellent choice. t is also possible to pre-compile your application's source code to native code and embed MacRuby. Laurent On Nov 23, 2009, at 1:27 PM, Matthew Winter wrote:

Hi,

I was wondering if anyone thinks or has plans to use MacRuby 0.5 for a commercial application.

My opinion is that with enough testing and waiting for the final 0.5 release that it would be good enough. Especially if the app can auto update so newer releases of MacRuby could be embedded.

What does the group think to this?

Regards Matthew Winter _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel