On Thu, Jul 3, 2014 at 6:37 AM, Cao, Jenny Q <[email protected]> wrote: > Kis and Anssi
Zoltan 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? Check XWALK-1103. It will be updated as soon as there is a new plan. I have an idea on it but I need to discuss with others. Mozilla correctly noticed the data duplication problem of DataStore, and that DataStore became more and more like IndexedDB. They intend to use named IndexedDB instead, and don't any more see much gain in standardizing the data sync part of the API. Makes sense to me. However, we do need a sync API, since we may have message/contacts/call history data sources ranging from Bluetooth MAP and PBAP to local native DBUS interfaces and local native databases. I will make a proposal, discuss it and I will implement it as soon as I finished the Telephony API implementation. I would not include a generic search API at this point (i.e. we don't implement the Tizen mobile API's). The reason is that a search API would only work with local native database sources, and we also have others which won't support it, and we would need to cache the data in the extension for providing generic database search, with questionable performance and benefits. But later we may decide to support the simple data models in the current versions of the Contacts and Messaging API spec, in addition to the sync API, which covers 90% or more of the app needs. Mozilla contested the idea saying that it's one kind of a data model and how do we know it's good enough for all the apps. Instead we should just give them the data, and let them organize it in an own DB. There is a point in that, too. So at the moment we will skip the search API until we get developer feedback, and the SAPI idea also gets more clear (tested). It's better to add later than screwing it up now, with a lot of effort. Best regards, Zoltan > 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 _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
