I agree with you Axel, I got it working. But shouldn't have had to do so. The larger moose is version compatibility. The industry standard is two versions back the API should work. Apache does not honor this. Now, Google is not either. It is PAINFUL to partner. In my case, 10 hours plus future maintenance headaches.
Well, its a great platform nonetheless. Just in its infancy I guess. Tim On Thu, Nov 26, 2009 at 10:44 AM, axel <[email protected]> wrote: >> You will need to use reflection (or intelligent class loading) and use >> the ContactsContracts provider when running on Android 2.0, allowing >> your existing Contacts code to be used on 1.5/1.6. > The Contacts.ContactMethods API is deprecated but not dropped. And > even deprecated APIs are required to function properly. > Google has to make sure (and even stated it in this forum) that this > is the case. It cannot be the idea for applications to check the > Android version invoke APIs accordingly via reflection. > I don't like to receive complaints from user that my application > doesn't work properly on their phone but if Google doesn't ensure that > event deprecated APIs, it is not my fault. > If many developers (especially of free applications) think likewise > user will experience a increasing number of non-working applications > in the Android market. > But thanks for your reply anyway :-) > > Axel > > -- > 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 -- 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
