@Dianne, We're using the Android API in a way completely consistent with the documentation. If device OEM's decide not to implement some of the API, we will have to make adjustments, as described in my post above.
I think concerns over fragmentation are more about devices with proprietary, non-standard APIs, and not so much with OEMs choosing not to implement some of the API. Eventually, the parts of the API that have been ignored by OEMs will have to be deprecated, or updated with comments like "Not Supported on Samsung Devices," or "Returns a constant value on Motorola devices," or something like that. In any case, no type of fragmentation would occur if everybody stuck to the published API. Finally, it is our hope that the number of pre-2.0 devices released will start to drop, and the number of 2.0+ devices will increase, such that we won't have to be making adjustments for long :-) Scott SoftwareForMe.com On Wed, Jan 27, 2010 at 10:21 AM, Dianne Hackborn <hack...@android.com>wrote: > On Wed, Jan 27, 2010 at 9:31 AM, SoftwareForMe.com SoftwareForMe.com < > softwareforme....@gmail.com> wrote: > >> The issue in this thread was that it is possible to simulate it on all but >> one [known] Android device from 1.0 though 1.6. As I said above, our >> software uses a different code path on 2.0 and later devices, so there are >> no ill side effects when placed on new devices. >> > > Wow. Okay, all I have to say is this: please do not be one of the people > who complains about fragmentation, and please provide HUGE CAVEATS to > -anyone- who is giving any thought to using your code. You are entirely > relying on certain behavior, of a certain vendor's certain screen, that will > not happen on most other screens. You can guarantee that this code will not > work or work poorly or various devices as they ship. > > It's a clever trick for the cases where it works, but relies on highly > variable behavior between devices. > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
