On Dec 12, 5:30 pm, TreKing wrote: > Replying back to the whole list. Oops. Thanks for the catch.
> On Mon, Dec 12, 2011 at 6:06 PM, Chris Ostler <[email protected]>wrote: > > On Dec 12, 4:37 pm, TreKing wrote: > > > On Mon, Dec 12, 2011 at 2:07 PM, Chris Ostler wrote: > > > > I'm interested in building an alternative backend service for use by the > > > > android.location.Geocoder class. > > > > Are you talking about updating the existing Geocoder class? Because you > > > should consult the platform or porting group for that. > > > As per the documentation, the Geocoder class requires a separate > > backend service that actually does the geocoding. I'm wanting to put > > together an implementation of this service *different* than the one > > provided in the Maps API package. > > It's not in the Maps API package - that's a separate library - Geocoder is > in the core platform. > > "The Geocoder query methods will return an empty list if there no backend > service *in the platform*. Use the isPresent() method to determine whether > a Geocoder implementation exists." > > That to me sounds like you'd have to modify the firmware. Perhaps I'm misunderstanding how the pieces fit together, then. I thought that: * The Geocoder class communicates with an on-device backend service to get the geocoding result * The Maps API package provides an implementation of that service The sentence just before what you quoted states: "The Geocoder class requires a backend service that is not included in the core android framework." The way I read that is that the Geocoder class in the core framework requires a service that is not in the core framework. The services available on a device, in combination with the core framework constitutes "the platform" in the sentence you quote. Perhaps I'm misunderstanding? > > My goal is to allow existing apps that currently use the Geocoder > > to function correctly when no network access is available (which > > is required by the Maps API provided service). > > Geocoder is not required by the Maps API. What I was trying to state was that the backend service for geocoding provided in the Maps API package requires network access. I guess I wasn't clear in my formulation. I've been assuming that since the background service was provided in a separate package, that it was somewhat modular and thus amenable to having an alternative implementation provided. Am I being too optimistic? Is the service actually tightly joined to the core Android framework, such that this wouldn't be possible? -- 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
