Very nice. symbol hound just isn't that great so it's good that at least rubydocs can be searched properly for that spaceship and stuff. aw, can't find the stabby lambda, but at least you've got a nice 404 page :) http://www.omniref.com/?q=-%3E
We need to give more love to symbol search - most are fine, but the query analyzer doesn't do well with all combinations. We'll add that one to the bug list.
Tim & I are planning to spend quite a bit more time on this, what do you other devs want to see in documentation search? Full stack? Multi version? Comments? Examples? IDE integration? What would make your life better?
I don't know what options are valid in `cache_action`. The "real" answer, AFAICT, is to keep walking up the source code until you find the AbstractWhatever that actually defines the options.
Yeah, rails makes this as hard as possible to figure out, because everything is done dynamically by Hash arguments. Maybe we can do something like like link up the inheritance tree from the method?
Some feedback I have, is that I would like the sidebar to have a view that was less 'cluttered'. I know what String#new does, so could I just view all the methods available - sans description? Like how ruby-doc does it, super fast to spot what I need to lookup and click it.
Another is that the sidebar seems to take up a fair bit of space (especially as I use a half-sized browser window).
I really want to see this flourish, it seems a lot faster than searching ruby-doc! Keep at it, guys! :)
Yep, that's it. Would love to just click the one from the results, then have that view. But if I have to then click the name on the right, that's fine too.
I would like to have code examples in many libraries. But I'm not sure how you could achieve this... Maybe linking stackoverflow related posts in some way.
We already have all of the documentation for all of the current ruby gems, plus the ruby standard library. We don't yet have all versions of everything, but that's coming soon.
AFAIK, we're already more comprehensive than the existing sites, though.
Anyone looking for functionality like this in a local, offline reference should check out YARD[1]. I (embarrassingly) only recently set it up to serve a set of my common gems and the ruby standard lib and it works and looks great.
You should be careful with YARD -- we've found a number of bugs in it that lead to broken/missing documentation. The ruby standard library, for example, is missing huge chunks of its documentation if you use YARD instead of RDoc.
I very much wanted YARD to be a drop-in replacement for RDoc, but it's not quite there yet.
I've always liked what Mercurial's docs were trying to do (http://hgbook.red-bean.com/read/customizing-the-output-of-me...) by having comments at every paragraph of their docs. It's done about 10% as well as it could be though. You almost want stackoverflow style questions to link to direct paragraphs or maybe even sentences.
Maybe overlaying something like rap genius' tools on existing docs is enough?
Looks really nice so far, but I don't use ruby so can't vouch for accuracy of search etc...
I like the speed of the search and most of the layout. It could really use some kind of Table of Contents for the current entry, though.
For more fanciful ideas, it would be neat if there was a way to add links to particular paragraphs or sections so you can link to any relevant blog posts or StackOverflow questions that explain the intricacies of something in more detail. Especially if it was easy for readers to add them in themselves.
We do have a ToC view for everything we index, it's just not totally obvious how to get to it right now (from search, click on the header in the preview window -- those links go to the view you want). For example:
That said, you're totally right about this needing to be more visible, and we'll have something better for this in the next day or so.
"it would be neat if there was a way to add links to particular paragraphs or sections so you can link to any relevant blog posts or StackOverflow questions that explain the intricacies of something in more detail. Especially if it was easy for readers to add them in themselves."
We've had multiple requests for comments, so that's definitely going on our short list of new features. Thanks for the feedback, and let us know if you think of anything else.
Very nice. One note though. When I look for "puts", I get OpenSSL::Buffering#puts when I'd expect Kernel#puts. "kind_of" gives me RSpec::Mocks::ArgumentMatchers#kind_of. I think you should assign proper weights.
We've done a lot of work to weight things correctly (e.g. searching for "inject" does what you'd expect), but we definitely need to do more work on really common tokens like "puts".
We'll add those to our bad search list. Thanks for the feedback!
We're looking at several other signals than tf/idf right now, but the really big improvements in quality will come from static & runtime analysis of all the publicly available ruby code for just this sort of case. I'll make sure these get added to our ever growing list of QA queries so we can make sure they improve.
Right now, the Table of Contents navigation is only visible on full documentation pages, but I'm working on some javascript to make it work in a nice way for the search results previews too. Also working on making it more obvious how to get to the full doc pages as well.
Improved crossreferences! The main problem with Rails docs today is that methods mention other methods by name, but there's no way to jump directly to that other method.
It's pretty tough to always know the right method in the general case (e.g. method from another module), but we think have some ideas that we're working on that will greatly improve this.
If nothing else, we can trigger a search for methods with that name. We're going to do that very soon, actually.
If your gem is published, we'll pick it up automatically during the next index run. If not, we're thinking about adding the ability to index public repos -- but private ones are longer-term. What do you need?
http://www.omniref.com/?q=+
http://www.omniref.com/?q=[]
http://www.omniref.com/?q=-
http://www.omniref.com/?q=*
Quick tip: You have this tiny styling issue here: http://i.imgur.com/4uxUuPO.png