If you're using the ones at api.rubyonrails.org, then *of course* you're
having trouble navigating them. Tryhttp://www.railsbrain.comorhttp://www.railsapi.com-- same info, but more easily searchable.
That's very useful, many thanks. Bookmark x 2!
Read docs for whole classes, not just isolated methods. That will help.
I have! and the preambles, similar methods, etc. I always start at
the top, then look down
Ruby and Rails are more than just collections of methods. Read the
class preambles (Rails) and the pickaxe book (Ruby), and make sure you
I learned Ruby from the pickaxe book when there were no other docs
around Ruby is my go-to language now--I just maintained a bit of
non-Rails code this afternoon before turning back to this list,
discovering (OT, sorry) that Snow Leopard broke the Tk bindings.
Bleacch. But there is a difference between the structures that Ruby
allows you to do and what Rails needs you to do. In Ruby, you can do
something inelegant, but it works. That can be useful when you're new
to something, as you can get your feet wet, and then as you understand
what kinds of pithy expressions can replace the inelegant ones and
why, you "grow into" the language. Rails seems to be like that to an
extent, but the learning curve is steep. That's obviously a
consequence of one being a framework built on the other, but
nonetheless Rails seems harder to learn. It's OK--I may be dense as a
brick, but I'm stubborn, too.
If you're referring to my scolding,...
Actually as far as a RTFM post goes, it was extraordinarily
delicate It was more of darned-if-I'm-going-to-look-like-an-idiot-
again-tonight last night, but today I'm apparently back to happily
looking like an idiot.
Thanks for the links!