Recent Posts by Brian Marick

Topic: RubyCocoa / statusbar/speaking-statusbar-solution.rb

That looks like a leftover. Probably I was using this solution to explain the difference between RubyCocoa’s alloc.init() and pure Ruby’s initialize(). If you remove the initialize() you’ll see that all works fine.

I’ve changed the code; it’ll appear with the next beta.

Thanks.

Topic: RubyCocoa / Aleksey Gureiev - errata p. 134

(Trying to reach Aleksey because I can’t send mail.)

I don’t see how description could be called before the initialization finishes. Does the problem happen when you’re running the preferred-list app as it came out of the code files? Can I get a stack dump?

Topic: RubyCocoa / Leopard/Tiger RubyCocoa App

Did you try standaloneify?

You can install RubyGems in your third-party/lib package. Then it should be able to load gems in third-party/gems.

Topic: RubyCocoa / RubyCocoa Forum

https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Topic: RubyCocoa / Code example help (B1.0)

Is the problem running code out of the code distribution? If so, what code? If not, can you send me the code that breaks when you require, plus the fixed code? I’m at marick@exampler.com

Topic: RubyCocoa / Code example help (B1.0)

Perhaps it was an older version of Ruby, one that didn’t have Rubygems included in the distribution?

Topic: RubyCocoa / code for beta 2

That’s a little disturbing, given that the code hasn’t changed.

Topic: RubyCocoa / Controllers and Cocoa

I’m going to introduce an NSWindowController in the chapter I’m writing right now, where it’ll be used for a preference pane. Since so much of what NSWindowController does is tied to assumptions about a document-centric architecture, I’m planning on putting off most discussion until I have a chapter where I migrate the log from an ephemeral stream of text to a save-able document.

I was planning on moving the log from a stream of text in a text box to an editable tree structured view. I’m starting to wonder if I’ll have the pages to do that, though.

My teaching style tends toward the bottom up, so I’m more likely to show how to use lower-level building blocks before higher-level ones that (often) replace them. I’m not dogmatic about that, though.

Topic: RubyCocoa / Drag-and-drop example?

I’ve put a drag-and-drop example onto my plan. It will be dragging a directory from the Finder and dropping it onto a table field that holds a pathname.

Page limit is going to be a problem, so it might not make it in.

Topic: RubyCocoa / code for beta 2

This is fixed. However, it’s a more recent snapshot than the one that could have been made when the Beta 2 book was made. So there may be inconsistencies. I’ll rush out a beta 3.

Topic: Everyday Scripting with Ruby / Not able to install with setup.rb

Sorry for the delayed reply.

You’re right – the instructions are incomplete for OS X Leopard. When you run setup.rb, it puts the executables in a ruby-specific folder. You have to make symbolic links from /usr/bin to that folder. Like this:

sudo ln -s /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/clash-check.rb /usr/bin/clash-check.rb

Once you’ve done that, it works:

$ ruby -S clash-check.rb csv
DANGER: A library named csv already exists.

Note that you don’t need to use the -S on Unix systems (like MacOSX). You can run the script directly:

$ clash-check.rb csv
DANGER: A library named csv already exists.

If you don’t like messing with /usr/bin, you can put the Ruby-specific executable directory into your $PATH (not RUBYLIB). Like this:

export PATH=/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin:$PATH

That’s probably wisest – less chance later OSX upgrades will erase the symbolic link.

Topic: RubyCocoa / code for beta 2

Sorry for the delay – your note didn’t get filtered into the right folder in my newsreader. I’ll see what’s up.

Topic: RubyCocoa / textmate

Sadly, I’m not a TextMate user. (Aquamacs emacs, here.) I do have a chapter on how to use your favorite text editor + rake as an alternative to Xcode.

Topic: RubyCocoa / Table Of Content

http://media.pragprog.com/titles/bmrc/toc.pdf

At the moment, it shows the complete table of contents for beta 2, including placeholder chapters for topics not yet covered.

Topic: RubyCocoa / Running Statusbar.app on 10.5.2

Some people have had a problem. I’ve run it on two 10.5.2 machines (both intel) and not seen a problem. If you have this problem, can you tell me anything special about your configuration?

Topic: RubyCocoa / Code example help (B1.0)

Try this version

I didn’t do anything specific to fix the problem, but maybe it will provide more clues. Run the test suite, please.

Topic: RubyCocoa / Does MacRuby change the game?

My best guess at this point is that well over 50%, but less than 90%, of the material will be applicable to both RubyCocoa and MacRuby.

Topic: RubyCocoa / Ruby Cocoa 2.0?

There will be a discussion of memory management – might be a chapter on its own, might be part of the “how rubycocoa works” chapter.

Is there something specific that you’d like me to cover?

Topic: Everyday Scripting with Ruby / need svn for churnv7.rb?

Sorry for the delayed reply – I lost your note.

Yes, you need svn on the system – but not that most of the program can be tested without svn.

Topic: RubyCocoa / Testing

Dr. Nic noticed that I made an offhand comment about testing, then explored the source directory, noticed a pile of tests, looked at them, and requested more text about testing.

I am planning to have a larger chapter about testing later in the book. I’m still figuring out what style of testing I like for RubyCocoa apps. I’m starting off from an Atomic Object presenter-first style of test-driven design, but Cocoa makes some different assumptions (especially, I’m finding, when it comes to Cocoa Bindings, the topic of the next chapter).

So, just a warning: I wouldn’t take any of the test code in the various directories too seriously yet.

But I would welcome hearing what you want to see about a testing/design chapter.

Atomic Object style: http://www.atomicobject.com/pages/Presenter+First

Topic: RubyCocoa / Excellent book thus far

Thank you.

Topic: RubyCocoa / Code example help (B1.0)

I should have said “there may be a configuration problem here”.

Topic: RubyCocoa / Code example help (B1.0)

Hmm… there’s a configuration problem here. I think the sandboxing came after beta 1 of the book was cut. That means the code is out of sync with the book describing it, and the code snapshot might have come in the middle of my fiddling to get the sandboxing right.

I will investigate.

Topic: RubyCocoa / Offensive blurb

The attempt at humor was my fault. Sorry.

Topic: RubyCocoa / problems with multiple Ruby installations

Whoops – didn’t copy the important bit, which comes before the last para above:

To see what version of RubyCocoa you’re running, type this to <commandname>irb</commandname>: