cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bowser <bows...@gmail.com>
Subject Re: [Android] Deprecation of Geolocation on Android
Date Wed, 05 Feb 2014 19:32:25 GMT
We need to zero out the implementation so that it's just a config.xml
on Android.  Do we have an issue tracking this?

On Wed, Feb 5, 2014 at 11:19 AM, Mike Billau <mike.billau@gmail.com> wrote:
> So, any resolution on this? Anything special we need to do regarding the
> deprecation notice since we're not actually deprecating the plugin itself
> (need it to add the permissions) but rather just our implementation?
>
>
> On Tue, Jan 14, 2014 at 2:58 PM, Mike Billau <mike.billau@gmail.com> wrote:
>>
>> +1 to deprecate. Tested Web GPS on 2.3 (lowest that we have) and it worked
>> fine.
>>
>>
>> On Mon, Jan 13, 2014 at 1:54 PM, Joe Bowser <bowserj@gmail.com> wrote:
>>>
>>> So, an update on this.
>>>
>>> 1. Our users don't know how GPS works! I can reproduce Geolocation
>>> errors only by disconnecting my WiFi and by not having a SIM in the
>>> phone and expecting my GPS to magically get the signal from inside my
>>> office (It takes 2 minutes at least).  I can't change the laws of
>>> physics, so this is working as intended
>>> 2. Our GPS doesn't work any better or worse than Web GPS
>>> 3. We'll still have people filing bugs against the Geolocation plugin
>>> that I can't reproduce, I'd rather close them as Web GPS problems than
>>> "You've never used GPS before, I can't reproduce" problems.
>>>
>>> I think we should deprecate the code for the time being, since there
>>> isn't actually anything wrong with it other than the fact that it has
>>> a 60s callback (which was considered reasonable in the old days of
>>> 2008 when batteries died more quickly).
>>>
>>> On Sat, Jan 11, 2014 at 12:33 PM, Lindsey Simon <lsimon@commoner.com>
>>> wrote:
>>> > +1 to nuking it.
>>> >
>>> > Anyone depending on it for really old versions of Android is likely not
>>> > doing anyone a favor (themselves or their users) - and (I think) it
>>> > adds to
>>> > new developer confusion. Then again, having a plugin that only adds the
>>> > permission bit sort of does that too.
>>> >
>>> >
>>> >
>>> > On Fri, Jan 10, 2014 at 7:26 PM, Michal Mocny <mmocny@chromium.org>
>>> > wrote:
>>> >>
>>> >> Adding support for play services based geolocation could come as a
>>> >> value
>>> >> add later.  If the current implementation is broken and no one wants
>>> >> to
>>> >> work on it (seems to be the case since it hasn't been fixed yet), then
>>> >> Joe's suggestion to just drop it now and leave a no-op plugin that
>>> >> adds
>>> >> permission only sounds like the right thing short term.
>>> >>
>>> >> Joes first email claims Web Geolocation supports all current versions
>>> >> of
>>> >> android (http://caniuse.com/geolocation claims android 2.1+ though I
>>> >> didn't
>>> >> look in to possible quirks).
>>> >>
>>> >> -Michal
>>> >>
>>> >>
>>> >> On Fri, Jan 10, 2014 at 8:43 PM, Andrew Grieve <agrieve@chromium.org>
>>> >> wrote:
>>> >>
>>> >> > Is the plugin still needed on older android versions? e.g. we might
>>> >> > want to have it be a no-op based on the android version instead
of
>>> >> > deleting it?
>>> >> >
>>> >> > Android geolocation seems to have gone Play Services, so another
>>> >> > option would be to make the plugin use that instead of the OS
>>> >> > geolocation in order to provide some utility.
>>> >> >
>>> >> > On Fri, Jan 10, 2014 at 4:14 PM, Jesse <purplecabbage@gmail.com>
>>> >> > wrote:
>>> >> > > The index.html issue was iOS, not sure if it still exists.
>>> >> > >
>>> >> > > Windows Phone 7+8 use the browser based geolocation as they
have
>>> >> > > implemented the spec,  However because of the way permissions
are
>>> >> > managed,
>>> >> > > there is a native do-nothing stub that simply signal that
Location
>>> >> > Services
>>> >> > > are required.
>>> >> > > Windows8 does some massaging of the api to the WinJS version,
and
>>> >> > > adds
>>> >> > the
>>> >> > > permissions to the project.
>>> >> > >
>>> >> > > I just spoke ( physically ) with Joe, and with this change,
the
>>> >> > geolocation
>>> >> > > plugin would still exist for Android, it would just add the
>>> >> > > permission
>>> >> > > to
>>> >> > > the app.  So, Android's plugin would be almost identical to
WP7+8
>>> >> > > with
>>> >> > this
>>> >> > > change.
>>> >> > >
>>> >> > > +1 from me, assuming everything will just work.
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > @purplecabbage
>>> >> > > risingj.com
>>> >> > >
>>> >> > >
>>> >> > > On Fri, Jan 10, 2014 at 3:40 PM, Joe Bowser <bowserj@gmail.com>
>>> >> > > wrote:
>>> >> > >
>>> >> > >> It never did on Android, you can see this in Mobile-Spec.
>>> >> > >>
>>> >> > >> On Fri, Jan 10, 2014 at 3:39 PM, Brian LeRoux <b@brian.io>
wrote:
>>> >> > >> > Does the permission dialogue still ask for index.html
?
>>> >> > >> >
>>> >> > >> >
>>> >> > >> > On Friday, January 10, 2014, Joe Bowser wrote:
>>> >> > >> >>
>>> >> > >> >> Due to numerous issues found in Geolocation,
combined with an
>>> >> > increase
>>> >> > >> >> in reliability of the Web Geolocation, I'm wanting
to see us
>>> >> > >> >> EOL
>>> >> > >> >> the
>>> >> > >> >> Geolocation plugin.
>>> >> > >> >>
>>> >> > >> >> Reasons for this include:
>>> >> > >> >>  * Support for Geolocation on all currently supported
versions
>>> >> > >> >> of
>>> >> > >> Android
>>> >> > >> >>  * Numerous issues with the current Geolocation
plugin that
>>> >> > >> >> may
>>> >> > >> >> involve a full re-write of the Geolocation plugins.
>>> >> > >> >>  * The Web Geolocation may be more energy efficient
than our
>>> >> > >> >> own
>>> >> > >> >> Geolocation polling.
>>> >> > >> >>
>>> >> > >> >> What do people think about deprecating this plugin
and
>>> >> > >> >> recommending
>>> >> > >> >> that we use the browser's implementation on Android?
>>> >> > >> >>
>>> >> > >> >> Joe
>>> >> > >>
>>> >> >
>>> >
>>> >
>>
>>
>

Mime
View raw message