Right, that's why I want an index.

The online search facility has a few major flaws for this purpose:

1) It only works online - not, say, on an airplane (though that's
changing)

2) More importantly -- it's not a list. You can NEVER tell, via
search, whether you're using the right search terms and getting a
negative response, or you simply haven't guessed the right search
term. Search is not a reasonable substitute for an index.

3) For some keywords, search drowns you in irrelevant results. Which
makes #2 all the worse, as each negative takes a lot of time just to
discover it's negative. Instead, I try to remember where these things
live, and try there first, before I resort to search. When my memory
works, it's much faster, because then I have a simple list of a
relevant subset. When it fails, then I fall back on search.

But if you're advising developers, yes search is good advice. I should
probably direct my complaint elsewhere, where it might reach the
people responsible for the documentation.

On Feb 22, 4:46 am, Mark Murphy <[email protected]> wrote:
> Bob Kerns wrote:
> > I located them looking through platforms/android-2.1/data/
> > broadcast_actions.txt, which is a WHOLE LOT EASIER than looking in the
> > documentation, where this is scattered around.
>
> On the other hand, the ones in the documentation are the ones you are
> supposed to use. There are broadcast actions in that file that are not
> in the SDK (e.g., com.google.gservices.intent.action.GSERVICES_CHANGED)
> and should be avoided.
>
> > The downside is, we don't know what the documentation says about them.
> > I could grep through the documentation, but I'll leave that exercise
> > to you.
>
> The online version of the documentation has a nice search facility.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to