I suppose that there is probably several approaches to dealing with the situation at hand but after some quick checks online about it, I had conflicting thoughts as to what people were really doing/using. If one were to start testing communications with the ContentProviders and ContentResolver classes on the Android phone, it would be helpful if a couple applications that we would like to interact with could be tested through the emulator against our code that we are writing. If we were interested in getting data from a compass application that is freely available online for instance, then the developer would go download the application on the market and request information from the compass occassionally.
Other than calling an the activity itself from within the developers program and then returning to the program with the back key, it would be helpful to just grab the data about the orientation of the phone when requested (this is just an example of course). Can we not download an application from the market onto the emulator and then test communicate with the application? Hopefully we don't have to resolve to compile, load on the phone, debug in emulator, try again. What is the appropriate approach for a situation like this at the present state of the SDK and tools that are available to us? ~ JFrog "Debugging is twice as hard as coding something the first time. Therefore, if we write the code as cleverly as possible, we are by definition not smart enough to debug it."
-- 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
