Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F32B59DDE for ; Thu, 2 Feb 2012 22:03:51 +0000 (UTC) Received: (qmail 41880 invoked by uid 500); 2 Feb 2012 22:03:51 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 41757 invoked by uid 500); 2 Feb 2012 22:03:51 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 41749 invoked by uid 99); 2 Feb 2012 22:03:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 22:03:50 +0000 X-ASF-Spam-Status: No, hits=-1.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates 64.18.1.183 as permitted sender) Received: from [64.18.1.183] (HELO exprod6og102.obsmtp.com) (64.18.1.183) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 22:03:43 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob102.postini.com ([64.18.5.12]) with SMTP ID DSNKTysIKR/cT4KFSVS7SH8rnpcfOPgWOD2m@postini.com; Thu, 02 Feb 2012 14:03:22 PST Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q12M3KhO014755 for ; Thu, 2 Feb 2012 14:03:20 -0800 (PST) Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id q12M3GPo016465 for ; Thu, 2 Feb 2012 14:03:19 -0800 (PST) Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas01.corp.adobe.com ([10.8.189.99]) with mapi; Thu, 2 Feb 2012 14:03:17 -0800 From: Filip Maj To: "callback-dev@incubator.apache.org" Date: Thu, 2 Feb 2012 14:04:37 -0800 Subject: Re: orientationchange event in cordova Thread-Topic: orientationchange event in cordova Thread-Index: Aczh9nd8dE9p5s1xQ7SDLogeK5P8Og== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Do we need a vote thread or something to get API changes/updates approved? What's the right way to go about this? In terms of issues and whatnot its clear (docs first, then JS API, then finally native implementations) but I'm more wondering about the discussion/voting/API change process. On 12-02-02 1:58 PM, "Brian LeRoux" wrote: >+1 orientationchange api > >(should file a jira to make note of all this in the docs) > >On Thu, Feb 2, 2012 at 1:46 PM, Filip Maj wrote: >> The deviceorientation event is a W3C spec, whereas the orientationchange >> event is an apple standard I believe >> >>=20 >>http://developer.apple.com/library/IOs/#documentation/AppleApplications/R >>ef >> erence/SafariWebContent/HandlingEvents/HandlingEvents.html >> >> I am generally in favour of following the w3c however I personally like >> the orientationchange event API better... D: >> >> >> On 12-02-02 12:41 PM, "Jesse" wrote: >> >>>No, not to that spec. However it is mentioned in the section: >>>"... may be able to do so with the existing *orientationchange* event." >>> >>>Overall, it is a much simpler API where: >>>a) window.orientation holds the current value of one of [0,90,-90,180] >>>b) window fires orientationchange event when it changes >>> >>>Currently consistent in BB-WW, iOS, Android, WP7 >>> >>>In PhoneGap, the ability to generate the event may be governed by other >>>platform specific ways of defining what orientations the application >>>supports. >>> >>> >>> >>>On Thu, Feb 2, 2012 at 11:48 AM, Drew Walters >>>wrote: >>>> >>>> Is this implemented according to this spec or something different? >>>> >>>> http://dev.w3.org/geo/api/spec-source-orientation.html >>>> >>>> On Thu, Feb 2, 2012 at 1:43 PM, Filip Maj wrote: >>>> >>>> > Im sure it's all doable on the platforms, the question being posed >>>>is >>>> > "should this be part of the core cordova API?" >>>> > >>>> > I'm for it. >>>> > >>>> > If it's a yay, then we need to >>>> > >>>> > 1. Update the docs >>>> > 2. Update cordova-js >>>> > 3. Add support to each platform >>>> > >>>> > On 12-02-02 11:23 AM, "Jesse" wrote: >>>> > >>>> > >WP7 also supports this event via PhoneGap + polyfill. >>>> > > >>>> > > >>>> > >On Thu, Feb 2, 2012 at 9:46 AM, Shazron wrote: >>>> > > >>>> > >> on iOS it is supported on the UIWebView 4.2.x and greater but we >>>> > >> polyfill support for iOS 3.x (which we are planning to remove >>>>support >>>> > >> for, don't know exactly when, 1.5 is as good as any time) >>>> > >> >>>> > >> On Wed, Feb 1, 2012 at 1:25 PM, Filip Maj wrote: >>>> > >> > Are we supporting this as part of our API? Apparently iOS >>>>supports >>>it >>>> > >> whereas im pretty sure most other platforms do not. >>>> > >> > >>>> > >> > https://issues.apache.org/jira/browse/CB-213 >>>> > >> >>>> > >>>> > >>