Thank you very much Jean-Denis, you've provided me with very valuable information.

My publisher and I have been trying to define the audience for the book and what content belongs to the book. We've been lacking feedback from readers like you, people experienced with Cocoa but looking to use MacRuby instead or with Objective-C.

I took note of everything you wrote and will do my best to cover all or most of the mentioned topics. Andy my editor suggested to start working on appendix for some of these topics we can't really find a spot for. We are also going to try to give more pointers to people starting with Ruby so even though we don't teach Ruby we can help the reader easily find the information he/she might be missing.

Caio, at this point, there aren't any tools that are mature enough and provide the type of features provided by Xcode.
I understand your interest, but writing a book is a lot of work and unfortunately, one has to make hard choices. That's exactly why I won't be covering HotCocoa or alternatives to Xcode :(

- Matt

On Fri, Feb 4, 2011 at 1:11 PM, Caio Chassot <lists@caiochassot.com> wrote:
On 2011-02-04, at 07:30 , Jean-Denis Muys wrote:
>
> I am at the other end of the spectrum: I am an experienced Cocoa/Objective-C programmer and a Ruby newbie.

And I'm back at the ruby expert, cocoa newbie, yet…

> I expect the book to address two facets of software development with MacRuby:

… I'm very much in agreement with the list of things Jean-Denis listed here.

I'd only add a complement to "Using Xcode with MacRuby": Using MacRuby WITHOUT Xcode.

Rubyists tend to like stuff simple: plain text files for configs, CLI-based tools. Interface Builder is more-or-less inevitable, but otherwise I'd love to stay away from Xcode, particularly as a build tool.
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel