A couple related questions: 1. Can we assume these permissions are now "standard" (as of 1.6) because they are declared in android.Manifest? Or should we regard them as non-standard because their string constants begin with "com.android." rather than "android."?
2. Is it possible for an app to use these permissions backward- compatibly? Apps can deal with the evolving API by loading the features dynamically using reflection or error detection, but the permissions necessarily hard coded in manifest, right? So an additional apk may be needed every time a permission is added? (Does the Android Market support this?) --Joe On Nov 24, 11:09 pm, Vamsee Kanakala <[email protected]> wrote: > John B. Hansen wrote: > > I'm developing now for Android 2.0 and the Browser Bookmarks and > > history are working again > > (in the Emulator and on my Droid). > > Thanks for the tip. It's a shame, but I guess I'll have to make my app > 2.x-only. > > Vamsee. -- 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
