In addition to option #2, you could write a small application that listens on the intent contexts and acts as a stub for the radar app you want to target. Just accept the data being passed in and send back some static dummy responses.
You can then deploy this dummy app on your emulator. This will allow you to continue testing your app on the emulator, and also inject all sorts of pretend results that the radar app might provide to reduce the amount of integration testing required. Regards, Sean On Fri, Jul 17, 2009 at 7:36 PM, Mark Murphy<[email protected]> wrote: > > Josh wrote: >> Is there a way to view the manifest for an app I have >> downloaded on my phone? > > Not really. There are methods on PackageManager that you can use to > interrogate what is on your system, but they are not strictly "viewing > the manifest". If your phone is rooted, there are more options; the fact > that the emulator is, to some extent, pre-rooted is one of the reasons > why the Market is not available on the emulator. > >> The second problem relates to developing on the emulator. There seems >> to be no way of downloading apps from the market onto the emulator. > > Correct. > >> For example, I know how to call the "radar" app, since it is listed on >> openintents.org, however I cannot run this on the emulator because I >> do not have the radar app installed. So how do I install apps from >> the market that I need for development on the emulator? > > Here are two avenues: > > Option #1: Get them from some place other than the Android Market. The > apps you seek may be on AndAppStore, or SlideME, or available for > download from a Web site, etc. If an app in question is not available > elsewhere, and it is free, ask the author to distribute it by some > off-Market means. > > Option #2: Get a device and use it for your interoperability testing, > using its copy of the Android Market to acquire the apps you want to > work with. You will want a device for testing in general before you ship > your application, anyway. The emulator is designed for basic development > purposes -- the further out on the edges you go (e.g., sensors, camera, > real GPS, application interop), the more likely it is you will need a > piece of actual hardware. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Android Training in Germany, 18-22 January 2010: http://bignerdranch.com > > > > --~--~---------~--~----~------------~-------~--~----~ 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] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
