Hi Ravi, I think the plan is OK. But as Gabriel pointed out, we would like to leave the JS APIs out of it and have the JS APIs to be how it is now being implement for Node.js, Tizen and Crosswalk.
The JS API spec is here: https://github.com/otcshare/iotivity-node/blob/master/spec/iot-js-spec.md#web-idl-of-the-javascript-api Sakari From: <iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org>> on behalf of RAVI NANJUNDAPPA <nravi.n at samsung.com<mailto:[email protected]>> Reply-To: "nravi.n at samsung.com<mailto:nravi.n at samsung.com>" <nravi.n at samsung.com<mailto:nravi.n at samsung.com>> Date: Thursday, October 8, 2015 at 08:34 To: RAVI NANJUNDAPPA <nravi.n at samsung.com<mailto:nravi.n at samsung.com>> Cc: iotivity-dev <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> Subject: Re: [dev] [request for feedback] Proposal - IoTivity Bindings Generation Using SWIG Dear All, Gentle reminder. In case of no issues on this proposal, I'll start working on this proposal. Thanks and Best Regards, N Ravi ------- Original Message ------- Sender : RAVI NANJUNDAPPA<nravi.n at samsung.com<mailto:nravi.n at samsung.com>> Chief Engineer/SRI-Bangalore-Open Source/Samsung Electronics Date : Oct 05, 2015 09:57 (GMT+05:30) Title : Re: Re: [dev] [request for feedback] Proposal - IoTivity Bindings Generation Using SWIG Hello Gabriel, Thanks for the information. As mentioned in the proposal document, the initial plan is to support for Python and perl language bindings. Once these are completed and depending on the community's response, we will take this further to consider other bindings. Thanks and Best Regards, N Ravi ------- Original Message ------- Sender : Schulhof, Gabriel<gabriel.schulhof at intel.com<mailto:gabriel.schulhof at intel.com>> Date : Oct 01, 2015 18:56 (GMT+05:30) Title : Re: [dev] [request for feedback] Proposal - IoTivity Bindings Generation Using SWIG Hey, all! We're already writing JS bindings for the CSDK to be used with node.js, and we have higher level binding that mimic the C++ API as well. Writing JS bindings is not as simple as producing them using SWIG. You need to know for which environment you wish to write bindings. Bindings for Chromium are completely different than bindings for Node.js, for example. As far as the node.js bindings are concerned, it might be beneficial to integrate them with iotivity itself, because the contents of the bindings is determined by the build flags used to build iotivity. For example, certain constants are not defined if remote access is not enabled, and they are defined otherwise. Right now, I have to parse the header files using a bash script, which is super-undesirable because it doesn't recognize which C preprocessor directives were used during the compilation of iotivity itself. In addition, the interface between node.js and the bindings to native libraries changes all the time - so much so, that a second project called "native abstractions for node" (NAN) has sprung up to provide C preprocessor macros and C++ classes that allow developers to address multiple versions of node.js using the same C++ code. https://github.com/otcshare/iotivity-node Cheers! Gabriel [cid:BGFC2LL5XOK0 at namo.co.kr] -------------- next part -------------- A non-text attachment was scrubbed... Name: 201510081105792_Z5JE7EUA.gif Type: image/gif Size: 13168 bytes Desc: 201510081105792_Z5JE7EUA.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20151008/33207cb3/attachment.gif>
