Re:Better Browsing for Ruby Developers
by ufmace on Friday August 15, 2014 @10:58PM
(#8185260)
+1 on 1. I look at Ruby class documentation a lot. I don't think I've ever wanted to look at the Ruby C source. I'm not sure what the point is of seeing them side-by-side. As far as I can tell, there isn't even any vertical correlation between the class documentation and the C code. Just the Ruby docs, please.
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @09:17PM
(#8185074)
Yep. We were too restrictive in our domain settings! We'll be pushing a fix soon, but it will take a little while to work through the approval process. I'll Tweet when there's an update (@omniref).
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @06:48PM
(#8184709)
Send me an email at support@omniref with your browser info (type, version, installed extensions, etc.) and I'll look into it.
That's tricky code to get right; github uses jquery-based fast-loading of their source pages, and the extension security models make it particularly difficult to detect the change events (especially on Firefox :-/).
Re:Better Browsing for Ruby Developers
by _mikz on Saturday August 16, 2014 @03:26PM
(#8187233)
Will do, but it is Chrome on Mac with Diasconnect and Adblock Plus and maybe some others. No exceptions in the console (global, not the background page one)
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @07:18PM
(#8184826)
I think you're having a different problem, actually -- the OP was having trouble with the GitHub integration. Send me an email at support@omniref with the same information, and I'll look into it.
This is the first wider release of the extensions, so I'm not surprised there are a few bugs. Thanks for bearing with us while we fix them!
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @07:23PM
(#8184840)
We've been thinking about other ways to do it (e.g. restricting via bloom filter), but ultimately, there's so much content on Omniref that we're going to match most queries for something.
It's disabled for incognito mode, and the query data is used only to hit our search index. If this is still an issue for you, we can put a setting in to allow disabling of this feature for privacy.
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @07:52PM
(#8184921)
We thought about that, but we have a lot of content. Perhaps if we just limited the filter to something like method/class/module/gem names it would work, but even that would hit on so many searches that most would be coming back to us. We'd be restricting the utility of the feature without much gain.
That said, we're open to suggestions on how to improve this. We're very respectful of privacy -- omniref is SSL-only, for example, and we don't save anything that could be traced back to a user or an IP.
Re:Better Browsing for Ruby Developers
by nilved on Friday August 15, 2014 @10:44PM
(#8185237)
I don't think a product that depends on reading my search history is ready for release. That's a serious invasion of one's privacy and something that will make lots of people (I would hope most) not consider installing it. Perhaps there could be a way to opt-in specific searches (but is it much different from a bookmark with a keyword in that case?)
Re:Better Browsing for Ruby Developers
by virtue3 on Friday August 15, 2014 @08:31PM
(#8185003)
We understand what you're saying. But you'll have to excuse us if we're still not comfortable with giving you all our information and then having to trust just your word on what you do with the data.
Re:Better Browsing for Ruby Developers
by timr on Friday August 15, 2014 @08:33PM
(#8185008)
Sure, I get it. We'll add a preference in for disabling this, but in the meantime, you vote with your installs. My point is only that we haven't yet thought of a way of implementing this feature that is likely to satisfy you -- but again, we're open to suggestions.
Re:Better Browsing for Ruby Developers
by tucosan on Saturday August 16, 2014 @07:07AM
(#8185884)
That would be which? Does the plugin send every search request made to google to the omniref servers?
Did you have a look at the implementation?
@timr could you give some more info on how you accomplish this?
1. I wish I could resize the code/documentation panes to give more space to the documentation, or even collapse the code compeltely
2. A little syntax highlighting in the method signatures in the documentation would be nice.
We're doing #1 -- look for that in the next week or two -- and I'll add #2 to our to-do list.
Any chance of getting that fixed?
That's tricky code to get right; github uses jquery-based fast-loading of their source pages, and the extension security models make it particularly difficult to detect the change events (especially on Firefox :-/).
This is the first wider release of the extensions, so I'm not surprised there are a few bugs. Thanks for bearing with us while we fix them!
It's disabled for incognito mode, and the query data is used only to hit our search index. If this is still an issue for you, we can put a setting in to allow disabling of this feature for privacy.
That said, we're open to suggestions on how to improve this. We're very respectful of privacy -- omniref is SSL-only, for example, and we don't save anything that could be traced back to a user or an IP.
(note: I'm one of the creators of Sourcegraph, would love to hear any feedback!)