Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of purdrew@gmail.com designates
 209.85.214.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADjNb+k2FCFDy+LL4sS2QrcQ3-+OYb_Ysor9d98p1U0VpW+Y3w@mail.gmail.com>
References: 
 <CADjNb+k2FCFDy+LL4sS2QrcQ3-+OYb_Ysor9d98p1U0VpW+Y3w@mail.gmail.com>
Date: Mon, 19 Mar 2012 09:54:32 -0500
Message-ID: 
 <CAO_65gz=SH=kbOL-+Kr9Q2L0tWCn5PfcJe6sEoDbb4enfmANfw@mail.gmail.com>
Subject: Re: Plan for device specific APIs?
From: Drew Walters <purdrew@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0015175cb68071eae704bb99bc9e

--0015175cb68071eae704bb99bc9e
Content-Type: text/plain; charset=ISO-8859-1

In the short term you can look at how BlackBerry uses the 'objects' and
'merges' objects in the platform file to do complete replacement or api
level overrides.
On Mar 19, 2012 9:46 AM, "Becky Gibson" <gibson.becky@gmail.com> wrote:

> What is the plan for the device specific APIs that have existed in the
> platform JS files?  For example,  iOS has a more efficient api for watching
> the compass heading,  watchHeadingFilter and clearWatchFilter.  iOS also
> has apis for bringing up the native contact picker to display, select or
> edit a contact.   Are we still going to provide those in the device
> specific js files? Will they become "general" plugins?  Perhaps an optional
> "core" plugin?  I don't think we should lose this functionality and it
> should somehow be available with 1.6.
>
> -becky
>

--0015175cb68071eae704bb99bc9e--