> This is one area > I'm a bit confused on. I don't really see how defining Intents can be > done well unless a central body defines them. For instance, my file > selector might expect a totally different intent from what yours > expects.
This is exactly the point that we try to address with our open source project OpenIntents ( http://www.openintents.org/ ). We define and implement commonly used intents in a way that should be consistent across various applications. For the case of picking a media file we have media browser and media player that closely work together: http://www.openintents.org/en/node/15 In fact, for those we did not have to define any new intents: If you call the media browser with the PICK intent or GET_CONTENT intent on audio, video, or image URIs, it will open the activity that lets you select a file from Android's media content provider and return that to the calling activity. If you start from the media browser directly and select a file, it will call the VIEW intent on the media file URI which will automatically start the media player. You can replace either media browser or media player or both by other applications. Full source code is available for download at www.openintents.org , but if you have further questions, don't hesitate to ask. Peli --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
