RickB wrote: > Anyone? Well, this isn't really the right list, since what you are describing is changes to the Android open source code, not developing applications to the SDK. If you elect to pursue this further, you might wish to post to a more appropriate list:
http://source.android.com/discuss >> My view is that it is not a good approach to create "sensor-specific" >> APIs with iterative releases of the Android platform and SDK's. By >> this, I mean that instead of adding a "location API", and an >> "accelerometer API", and whatever comes next, we should create a >> "generic" sensor API that can work with a broad range of sensor types, >> including sensor configuration, demand read/write/configuration, event >> notifications, and other functions. With the exception of location, that seems to describe quite nicely the existing sensor API. I imagine that part of the reason the location API is separate is because there are many possible "sensors" for location, and it could make the API rather cumbersome if every sensor had to deal with the possibility that there are several of its type, and to figure out which one is used, etc. Also, location requires permissions, whereas other sensors do not, IIRC. >> In this way, 3rd parties could >> also add innovative sensing capabilities (or external sensors) to >> their Android devices which would be "instantly" supported by the >> platform. Well-known sensor such as geolocation and acceleration >> could have agreed-to sensor names/namespaces, with full extensibility >> for additional sensor types. Again, outside of location, you seem to describe the existing sensor API. If you'd like to propose a replacement API, either to encompass locations or just a re-re-work of the existing sensor API more to your liking, give us some classes and methods to chew on...but perhaps in a more appropriate list. >> As an example, geolocation as a 2D longitude/latitude is fine for some >> apps, but for "inside the building" applications or for other apps >> involving the need to accurate location of people or resources in 3 >> dimensions, it doesn't cut it. FWIW, the existing location API supports altitude, assuming the underlying location provider offers it. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Need Android talent? Ask on HADO! http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
