Hello, I would like to open a discussion on what should be Tizen 3 unified strategy for Telephony management in Tizen 3. With integration in Tizen 3 of a Mobile profile just been started, I thought that the issue is ripe enough to be discussed.
In Telephony I would like to en-globe : - voice call - SMS/MMS - Contact 1) Need ----------- It should be possible to allow an App (HMTL5/Native) to : - offer to the user to make a phone call - offer the user to start a phone with a pre-entered number/contact - accept / reject an incoming call - send receive SMS/MMS (without or with out attachments) Obviously when using call or message services , the events related to these serives should be registered in the standard history data base in a same way as when created with the default platform applications. We should also be able to select the target device/firmware in charge of serving such communication request (Internal Model, Phone via Tethering, VoIP : eg Skype) 2) Architecture option ------------------------------ It is very unlikely that we will get the same low level middleware on all platforms and I do not believe that we can assume a unification at that level. That imply the creation of a set of unified APIs which can connect on different low level middlewares. The easy model would be to copy Android model where, an application willing to use a Com function (message, voice or contact) simply call an application in charge of handling the service. Alternative is to create a set of APIs which can be used by the App to initiate the Communication. The first model is far simpler and close to most Phone OS current mode of operation. It does present the main advantage of easing the coordination between Apps and platform base software but does not make that easy the provision of compliant W3C phone API which tend to work at lower level. http://www.w3.org/2012/sysapps/telephony/ The provision of a Dailer and a message handler with an enable remote control mode could be a valid option to serve both needs. Obviously that Dialer would have to be headless (no default UI) in order to let any platform to build their preferred solution adpated to their need. 3) How to move from here ------------------------------------ We have a well defined W3C API for Telephone and Message. Could we agree to use that as our base for a remote control of a Dialer ? We must have somewhere a set a CAPI for managing a dailer, message and contact hander in Tizen 2.3. Would that be a valid base for a dialer ? - can it be made headless ? - does it cover all requirements ? - do we have a documentation available somewhere in the Wiki ? Thanks in advance to help me to progress toward a unified solution. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
