![]() ![]() And also, its a great reason while I still use OmniWeb. This makes it so much easier to search the docs. I’ll take a look later and see if I can offer a fix. Okay, a nitpick with the bookmarklet: if I hit Escape it doesn’t cancel the search, but rather does a search for “null”. BUT the bookmarklet only uses a bit of my bookmarks bar, and by putting it near the beginning of my bookmarks bar (in Safari) I can get to it with Command-1 or -2 or whatever, with keyboard focus right where I want it. ![]() Well, the Safari extension returns the same four-column search results, and also includes links to key doc pages at. At any rate, bookmarklets are a good idea-good thinking. I hope I didn’t take too much creative license in filling them out. The filter sucks.Įrik: Your links should be effective bookmarklets now. I would assume any browser extensions use the filter field (which is powered by JSON), not the search. I’ll go through and fix up the markup on your comments. ![]() Weird, I’ve no idea why my “‘” characters got backslashed. Also you have to click on the field - it’s a pain to tab into. Or figure out from the source code how to do what Erik mentioned. Takes up some screen space, but one could add a keyboard shortcut for the menu item that toggles the view on and off. There’s a Safari extension called “ADC Search” that provides a dedicated text field that I assume does something similar. Please disregard my previous comment, I spoke without actually testing the links. Just drag those two links and rename the first one. But you don’t even have to go to the trouble of creating the HTML document anymore. Naturally I forgot to update the text in the anchor tag to “Search Mac”, and naturally WordPress ate my HTML. Save the following to a HTML document, then bookmark the links. Just create a two-line bookmarklet if you’re using a browser without custom searches. Apple’s had a bad habit lately of changing the links around for little to no apparent reason, with the result that Google-juice is not distributed as properly across Apple’s documentation as it once was.įorgive me if this is obvious, but you don’t even need to be using one of those browsers. I only wish Xcode’s built-in search were this good.Īnd, to be clear, that’s not Google’s fault. So far, Apple’s search (again, not the filter field) has worked very well. Often, it’ll only turn up the PDF, not the specific chapter I want in the HTML doc when it does show me what I want, it’s nowhere near the top. Google, whether I restrict to or not, has gotten pretty consistently bad for me. I’ve found that the order and quality of results are usually better from Googling site: than from searching directly on. 26 Responses to “Apple documentation search that works” You get the docs, the right docs, and nothing but the docs.įor this specific purpose, you now have something better than Google.Ĭategories: Cocoa Core Image Documentation Interface Builder iPhone Mac OS X Programming Quartz QuickTime Safari/WebKit Toolchain Xcode. No wild goose chases, no PDF mines, no third-party old backup copies, no having to scroll past six hits of mailing-list threads and Stack Overflow questions. You even get relevant technotes and Q&As. Then add one or both of these searches: For the MacĪDC iOS how the results page gives you both guides and references at once, even giving specific-chapter links when relevant. In OmniWeb, open the Preferences and click on Shortcuts: In Chrome, open the Preferences and click on Manage: Again, read on.)įirst, you must use Google Chrome or OmniWeb. That often isn’t much better than without it. You’ve probably been searching it like this: This isn’t just an easy way to use the filter field it’s an entirely different solution. You’ve probably tried searching Apple’s developer documentation like this:Įdit: That’s the filter field, which is not what this post is about. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |