Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB04A10DBD for ; Sat, 11 Jan 2014 03:27:20 +0000 (UTC) Received: (qmail 84746 invoked by uid 500); 11 Jan 2014 03:27:01 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 84712 invoked by uid 500); 11 Jan 2014 03:26:55 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 84661 invoked by uid 99); 11 Jan 2014 03:26:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 03:26:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates 209.85.212.42 as permitted sender) Received: from [209.85.212.42] (HELO mail-vb0-f42.google.com) (209.85.212.42) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 03:26:45 +0000 Received: by mail-vb0-f42.google.com with SMTP id i11so727101vbh.29 for ; Fri, 10 Jan 2014 19:26:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=KFeyVZtZwib/pBrREgntY+aa3qeXyjnU8HKEE56jIx0=; b=j3b5ku/mAZdaIH/DjbBr+sjNv1ZDz19kEqlNkhLvuP+rmsD9vI8CcMv/7GNRWOgR1N nS12hGA4GZ3BbyYmCT//6HTJ3qBuxy+mS/76f3lkcqmyBKGl9xPJaLrCUsdP/pKH5RH8 9YyHMywZ3C0mGKh9HdbM0cRX4/14MFuyB97EIXEHeafYCTx2azRZq/geEuCge+cwehLM Bt55x1AY1lOsGOgTWTvzVx39fyripsrSFXc7mTXxPF6rg5X2s3co+FY/w4kOazvl1p8a MSTiTWPI6McUvgh2K/X4aJcvjyTXgCxbjO/GHZK8Z+JTXoeix4N/f3I5jM+VOcgzmRD/ dk+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=KFeyVZtZwib/pBrREgntY+aa3qeXyjnU8HKEE56jIx0=; b=cu+usuDYGQXQ2ounxEvjvALqD3RQYbAxdeI+a24MZqIYFfqGQtwRnc2ex/QwF3ISs4 sVX/UY4SwmhoGoSQ1wAKjK0tc05bU2WAdvbEnz4DKme6oaJ57RtFnWMpGUnT+Hw/tHOd C3j2rNo4NClSfG8tJtSB3f0PU1hJuG+sJ3Xf4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=KFeyVZtZwib/pBrREgntY+aa3qeXyjnU8HKEE56jIx0=; b=YiB/MxByWl5rnCbQQwBXMiCvUq4mMC83rOAZsKy5nx4Fl202v3gHRZNJ8NUh6ex3e5 zLAz9G4TciUpnU4d2WgVjkLeY2zdviyc4MqjyBi7Cirux82YMD0/K/ghFQxRBdapRb0e LjicWutYMYQPKZJPh696oDiIOy7nJGp69w8eQroiYPnijbGAWLl7LhD9LB/YgDd0O0q+ VD1C/vFhq90q++UnIpvsQFQVODne8mi3OlrD7NBzNBMTbktjqYnklrrzPLlBQw8m0IUT w+oPUbohglaTsOigG6GQNRKi+c91PwbWj18thpB76R5qliE70tvj1YAc+PtrM+c25HqT sbQg== X-Gm-Message-State: ALoCoQldzyPgiVBbxOq20Wt6xnk86l85fO/yvq4CDAHHXORwkCtrijn95hdposiOfuVspcg3axWyLVvNA+BLVe/xS0GoCadKhKAcPunzBRcU/7K1UzgmFVKAz7xvmnlISHmNYEd3g9teEhuIfp+7EN3Rwn+TkDQkC2mclk2vRKKCfpylKOIVz1mjTbc5isZbe6ozQ5Go19sXIDLgDGqAGWUj/hJjhUvr+A== X-Received: by 10.52.245.42 with SMTP id xl10mr8974034vdc.35.1389410784270; Fri, 10 Jan 2014 19:26:24 -0800 (PST) MIME-Version: 1.0 Sender: mmocny@google.com Received: by 10.52.36.231 with HTTP; Fri, 10 Jan 2014 19:26:04 -0800 (PST) In-Reply-To: References: From: Michal Mocny Date: Fri, 10 Jan 2014 22:26:04 -0500 X-Google-Sender-Auth: _-z7I-TISkFn5PlfdZguh1Td4w8 Message-ID: Subject: Re: [Android] Deprecation of Geolocation on Android To: dev Cc: "bowserj@apache.org" Content-Type: multipart/alternative; boundary=089e015383803e713404efa968c3 X-Virus-Checked: Checked by ClamAV on apache.org --089e015383803e713404efa968c3 Content-Type: text/plain; charset=UTF-8 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 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 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 wrote: > > > >> It never did on Android, you can see this in Mobile-Spec. > >> > >> On Fri, Jan 10, 2014 at 3:39 PM, Brian LeRoux 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 > >> > --089e015383803e713404efa968c3--