Kis and Anssi
We have discussed about the Callhistory and Contact API last month, and you
mention that these 2 APIs would be based on the Data Store API.
I found that the DataStore API would be dropped from sysapps mailing list
What is the next step plan for Callhistory and Contact API for Crosswalk if the
DataStore API dropped?
Thanks
Jenny
-----Original Message-----
From: Kis, Zoltan [mailto:[email protected]]
Sent: Tuesday, June 3, 2014 12:43 PM
To: Cao, Jenny Q
Cc: [email protected]; Li, Cici X; Zhang, Zhiqiang;
Zhang, Belem; Zhao, Tina
Subject: Re: About the Modello phone UI and telephony and call history API
Hello,
On Tue, Jun 3, 2014 at 6:06 AM, Cao, Jenny Q <[email protected]> wrote:
> Zoltan
>
> I found that the modello UI phone functionality feature(xwalk-1661) will be
> supported in Crosswalk 7
>
> To support the phone functionality , Crosswalk need to support telephony API
> (xwalk-1419 future release)and Callhistory API(xwalk-1103 Crosswalk-8) on
> IVI,
>
> I have several questions about the telephony API and modello phone UI
>
> 1. About the spec,
>
> a) Telephony API: The crosswalk will implement the W3C sysapp
> telephony spec (http://www.w3.org/TR/2013/WD-telephony-20130620/) , which
> one will the modello phone UI use? Switch to use Sysapp telephony spec or
> keep using tizen phone API(no spec found from tizen API doc for telephony)?
Switching to use the W3C spec (which is to be updated based on last 2
F2F discussions), see the latest, but not final version here:
https://rawgit.com/sysapps/telephony/gh-pages/index3.html
>
> b) Callhistory API: The crosswalk will implement the callhistory
> part of W3C sysapp telephony spec, right? which one will the modello phone
> UI use? Switch to use Sysapp telephony spec or keep using tizen callhistory
> API
> (https://developer.tizen.org/dev-guide/2.2.1/org.tizen.web.device.apireference/tizen/callhistory.html)?
Switching to use the W3C spec, which is only a set of data properties.
Call History, Contacts and Messaging are to be supported through the
W3C DataStore specification.
http://airpingu.github.io/data-store-api/index.html
> 2. About the implementation schedule, the Telephony APIs and
> Callhistory API feature are target to later milestone than crosswalk -7,
> when the modello Phone UI support? After the full telephony and callhistory
> API feature supported? Or parts of the API supported ?
DataStore might be coming later, Telephony is targeted.
>
> I also note this question in the feature comments in xwalk-1661 in JIRA.
>
>
>
> 3. About the namespace, what namespace will be used for implement the
> telephony API,
>
> a) xwalk.experimental.telephonymanager,
>
> b) navigator.telephonymanager
navigator.telephony or <root-object>.telephony
>
> c) tizen.phone.
That is experimental for phoned, not official.
Best regards,
Zoltan
--- Begin Message ---
Hi. Marcos and Chris.
In case of Contacts Manager API, previously we had long discussion for apply
DataStore API to Contacts. But as Marcos said DataStore AP was dropped. So I
would like to know which kinds of outstanding issues are there in the spec?
It's quite long time ago, but as far as I remember, there are not many major
issues. Is it right? Also I would like to know the next step for this.
Kr, Wonsuk.
2014-06-27 2:36 GMT+09:00 Wonsuk Lee
<[email protected]<mailto:[email protected]>>:
Hi. Marcos.
Thanks for reply!
I added inline comments.
2014-06-27 0:23 GMT+09:00 Marcos Caceres
<[email protected]<mailto:[email protected]>>:
On June 26, 2014 at 11:00:44 AM, Wonsuk Lee
([email protected]<mailto:[email protected]>) wrote:
> Hi. Editors!
> I would like to know exactly about current status and next step of contacts
> API, Data Store API and TCP and UDP Socket API specs. What are outstanding
> issues or blockers for them?
We want to drop DataStore - we don't want to standardize it. We ended up using
named IDB stores in FxOS instead.
Can I ask reason why to make that kind of decision? Gene also agreed with this
decision. right? just want to know :-)
We need to settle on the underlying Stream before TCP/UDP can happen.
Do you know status of Stream API spec? When do you expect that Stream API will
be be settled down?
Kr, Wonsuk.
--
=========================================
이 원 석 (Wonsuk, Lee) / Principal Engineer, Ph.D
SAMSUNG ELECTRONICS Co., LTD. (三星電子)
Mobile: +82-10-5800-3997
E-mail: [email protected]<mailto:[email protected]>,
[email protected]<mailto:[email protected]>
http://www.wonsuk73.com/, twitter: @wonsuk73
-----------------------------------------
Inspire the World, Create the Future !!!
=========================================
--
=========================================
이 원 석 (Wonsuk, Lee) / Principal Engineer, Ph.D
SAMSUNG ELECTRONICS Co., LTD. (三星電子)
Mobile: +82-10-5800-3997
E-mail: [email protected]<mailto:[email protected]>,
[email protected]<mailto:[email protected]>
http://www.wonsuk73.com/, twitter: @wonsuk73
-----------------------------------------
Inspire the World, Create the Future !!!
=========================================
--- End Message ---
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
