From: benjohn@...
Date: 2006-05-10T16:23:07+09:00
Subject: Re: Ruby documentation discovery

*snip*

> I saw some code that said "require callbacks". I saw that it referenced
> a
> Callback class. So I went to the terminal and typed ri Callback, but ri
> said
> nothing was known about Callback.

I believe your post is about documentation, rather than callbacks.
However: a "callback" is a general term. It's a function / method that
you register with some entity, so that when that entity encounters a
particular type of event, it will call the registered function. An
example: A widget library may have a button entity. The button entity
may have an "on click" handler that you can register a call back with.
You may register a function that pops up another window, or fires a
space ship's gun.

There may not be an actual call back class. In Ruby, a call back can be
extremely well modled with a Method object.

*snip*

> I'd also love to hear from anybody who shares my frustration (am I
> alone?)
> as well as any ideas for going forward. Are there any efforts afoot
> where I
> could lend a hand?

You're not alone. I've found that the thing I love about Ruby is how
well it works out of the box (that, and its simplicity, power and
consistency). It is easy to start playing and discovering. The
documentation doesn't seem to have this property so strongly though. I
think I must be missing some important knowledge of the tools in this
arena, but I've not yet found the answer.