> The strangeness is not just limited to the lack of a discovery API. What I'm trying to say is, even if they were discovery APIs they would be of limited use, because they could never tell you which extras you have to use, what they mean, and how to interpret the result.
The only thing that can help you is better documentation. > There's also a peculiar lack of documentation on what the built-in > apps can do, leaving us wasting a lot of time poking about making up > intents by experiment. For built-in apps, you can always look into the source code to see what their intents expect: http://android.git.kernel.org/ (see platform/packages/...) For some applications, the developers update their intents themselves already at OpenIntents.org and document them over there. See e.g. http://www.openintents.org/en/node/94 Some intents are frequently asked for, so that we have small code snippets: http://www.openintents.org/en/node/121 If you use undocumented intents by closed source applications that the developer did not publish information about, chances are the developer may change the intents anytime, so your application could break if you use their intents... Is there a specific application you would like to know more information about? Peli www.openintents.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
