Hi lecouvey, >Is it a problem to use BlueZ default agent ? You can use Bluez default agnet to test.
>Nonetheless, Let me know if you want that I send a draft patch in gerrit. If possible, we hope check your source code. >Btw, have you finished NTB code ? We finish the almost all BT CAPIs. We are being TCT test. Only the CAPIs of Bt_socket_accept still is being implemented. The interface design of Bt_socket_accept doesn't very match Bluez-5.X designing. However, we are implementing it. It will be finished next week. Best Regards Zheng Wu From: [email protected] [mailto:[email protected]] Sent: Thursday, June 26, 2014 11:14 PM To: Zheng, Wu; Le Foll, Dominique Cc: [email protected]; Xu, Martin; Jia, Pei P Subject: Re: About New Bluetooth-Frwk(NTB) plan Hi all, About NTB integration in Tizen Common, my main concern is the popup system used. On Common/IVI, we removed the bluetooth syspopup agent (bt-syspopup) in order to use notification-service. By this way, we do not depend on any graphical display systems and toolkits. Then homescreen will subscribe to notification-service in order to display relevant popups. I'm working on implementing NTB popups system based on notification API. I've done a bluetooth text notification client and I'm able to pair my device. User confirmation reply is done with a dbus reply method as it is currently done. Do you see any problem in this implementation ? This solution is not compatible with the new bt_agent_xxx C API. This new C API allow to register a specific Bluez Agent. In my case, I don't have a specific BlueZ agent and I use the BlueZ default agent. Is it a problem to use BlueZ default agent ? Now I would like to know if it is an acceptable solution before cleaning the code and implementing all of the use cases... Nonetheless, Let me know if you want that I send a draft patch in gerrit. Btw, have you finished NTB code ? Best regards, Corentin Le 17/06/2014 10:18, [email protected]<mailto:[email protected]> a écrit : Hi Zheng Wu, This is good news. About TCT Web API testing, be aware that the bluetooth crosswalk extension based on Tizen C API is not integrated yet. It is waiting for a code review. https://github.com/crosswalk-project/tizen-extensions-crosswalk/pull/308 I will be glad to help you for NTB integration in Tizen common and TCT testing. Best regards, Corentin On 06/17/2014 08:15 AM, Zheng, Wu wrote: Hi Dominique, The coding of New Bluetooth-Frwk(NTB) will be finished in this week. We will start NTB TCT testing soon. We hope work together with your team to test New Bluetooth-Frwk(NTB) TCT on Tizen. Do somebody in your team member want to join New Bluetooth-Frwk(NTB) TCT testing on Tizen? And can you provide the schedule of Tizen-3.0 Common? So that NTB can finish TCT testing and merge to Tizen-3.0 Common before Tizen-3.0 Common code freeze. Thanks. Best Regards Zheng Wu
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
