tags:

views:

12

answers:

0

When I write Java in Eclipse, I can point to pretty much any declaration or method invocation and instantly get the relevant Javadoc for the class or function I'm interested in. I guess it's spoiled me a bit -- rarely do I have to poke through the API documentation by hand, and frankly it's a nice feature to have.

I've been doing Ruby development for quite some time now, and while I've managed to work out a pretty good system for finding docs when I need to answer a question, it's not quite as quick or reliable as the automated system for Java projects. I realize that "do what I mean" with Ruby code is a lot trickier since scope and typing aren't easy or even always possible to deduce without running the code, but I feel like at least I could get a choice of possible matches, and most of the time I don't even get that.

For example, I'm developing a small app in Camping, and though the runtime knows that there are libraries and rdocs in my $GEM_HOME, Eclipse's documentation magic doesn't seem to find them at all -- highlighting the word "link" (the Markaby function / tag) gives me the docs for Pathname::link, with no option to look for extra stuff.

Am I stuck with what I've got? Are there some settings I can try to tweak somewhere? Is there a better Ruby IDE I should be using?