atom feed14 messages in org.apache.incubator.callback-devRe: Plan for device specific APIs?
FromSent OnAttachments
Becky GibsonMar 19, 2012 7:45 am 
Drew WaltersMar 19, 2012 7:54 am 
Gord TannerMar 19, 2012 7:58 am 
Patrick MuellerMar 19, 2012 8:23 am 
Becky GibsonMar 19, 2012 9:16 am 
Patrick MuellerMar 19, 2012 9:37 am 
Becky GibsonMar 19, 2012 10:15 am 
Jesse MacFadyenMar 19, 2012 10:37 am 
Filip MajMar 19, 2012 10:42 am 
Filip MajMar 19, 2012 10:46 am 
Patrick MuellerMar 19, 2012 11:09 am 
Becky GibsonMar 19, 2012 12:08 pm 
Filip MajMar 19, 2012 12:15 pm 
Patrick MuellerMar 19, 2012 1:45 pm 
Subject:Re: Plan for device specific APIs?
From:Drew Walters (purd@gmail.com)
Date:Mar 19, 2012 7:54:09 am
List:org.apache.incubator.callback-dev

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" <gibs@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