Hi. Sakari. Thanks for bringing nice item to Iotivity. I believe it will provide better development environment for makers of IoTivity products.
Regarding the proposal I have below questions. 1) I think if you consider Iotivity js framework on the node it would be okay for smart phone and tablet, but it might be heavy for small things. 2) Do you consider to support IoTivity hybrid app development using crosswalk? If it's ture, could you share which kind of architecture do you have in mind? Thanks. Kr, Wonsuk. > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Poussa, Sakari > Sent: Saturday, June 27, 2015 4:49 PM > To: ???(Uze Choi); nravi.n at samsung.com; iotivity- > dev at lists.iotivity.org > Subject: Re: [dev] JavaScript API for IoTivity > > Hi Uze, > > Thanks for sharing. Useful data. We?ll take a look once we have a slot. > > Thanks, Sakari > > From: "??? (Uze Choi)" <uzchoi at samsung.com<mailto:uzchoi at samsung.com>> > Date: Friday, June 26, 2015 at 10:14 > To: Sakari Poussa > <sakari.poussa at intel.com<mailto:sakari.poussa at intel.com>>, > "nravi.n at samsung.com<mailto:nravi.n at samsung.com>" > <nravi.n at samsung.com<mailto:nravi.n at samsung.com>>, "iotivity- > dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>" > <iotivity-dev at lists.iotivity.org<mailto:iotivity- > dev at lists.iotivity.org>> > Subject: RE: [dev] JavaScript API for IoTivity > > > Hi Sakari, > > > > >> 2. Only iotivity base (core) at the moment. We don?t understand the > services etc well enough to create anything there now. > > > > Currently Primitive Service Project the develop the abstracted easy API > for the Smart Device developer which will be released in the July. > > For example, we need to handle the whole communication sequence thru > Base API, However, we are developing the Data Centric API which is > called Resource Manipulation API. > > I believe this level of API is also suitable to JS porting. > > You can look over the wiki page for this detail explanation. > https://wiki.iotivity.org/resource_manipulation > > Please give your opinion for our idea. > > > > API prototyping signature is as follows. > Category > > Class > > API > > Parameter > > Return > > Server > > ResourceObject::Builder > > Builder > > const std::string& uri, const std::string& type, const std::string& > interface > > Builder& > > setDiscoverable > > bool > > Builder& > > setObservable > > bool > > Builder& > > setAttributes > > 1. ResourceAttributes& > 2. ResourceAttributes&& > > Builder& > > create > > void > > std::shared_ptr > > ResourceObject > > setAttribute > > std::string& key, const T &value > > void > > getAttribute > > std::string& key, > > template< typename T > > > notify > > void > > void > > setSetAttributeRequestListener > > const std::string& key,SetAttributeRequestListener (Function ptr) > > void > > removeSetSetAttributeRequestListener > > const std::string& key > > void > > Client > > DiscoveryManager > > discoverResource > > const std::string& host, const std::string& resourceURI, > OCConnectivityType connectivityType, DiscoverCallback callback > > void > > RemoteResourceObject > > startWatching > > ResourceStateChangedCallback > > void > > stopWatching > > void > > void > > startCaching > > void > > void > > stopCaching > > void > > void > > getCachedAttributeValue > > const std::string& key > > templete T > > getAttributeValue > > const std::string& key , (Function ptr) > > void > > setAttributeValue > > const std::string& key , (Function ptr) > > void > > getUri > > void > > string > > getAddress > > void > > string > > getTypes > > void > > vector< string > > > getInterfaces > > void > > vector< string > > > > > > BR, Uze Choi > > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev- > bounces at lists.iotivity.org> [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Poussa, Sakari > Sent: Thursday, June 25, 2015 7:39 PM > To: nravi.n at samsung.com<mailto:nravi.n at samsung.com>; iotivity- > dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> > Subject: Re: [dev] JavaScript API for IoTivity > > > > Hi Ravi, > > > > 1. The JS binding on the node is on top of the iotivity C API. On > Crosswalk it is on top of the iotivity Android Java API. > > 2. Only iotivity base (core) at the moment. We don?t understand the > services etc well enough to create anything there now. > > > > Sakari > > > > On 6/25/15, 13:32, "RAVI NANJUNDAPPA" > <nravi.n at samsung.com<mailto:nravi.n at samsung.com>> wrote: > > > > >Hi Sakari, > > > > > >These might be basic questions though but I do have couple of queries > > >here. > > > > > >1) Is this JS binding supported on top of C/C++ SDK Apis OR is it a > > >parallel layer to CSDK ? > > >2) Does this support only iotivity base or anything else as well ? > > > > > >Thanks and Best Regards, > > >N Ravi > > > > > >------- Original Message ------- > > >Sender : Poussa, > >Sakari<sakari.poussa at intel.com<mailto:sakari.poussa at intel.com>> Date : > >Jun 25, 2015 > > >15:25 (GMT+05:30) Title : [dev] JavaScript API for IoTivity > > > > > >Hello all, > > > > > >IoTivity is missing the JavaScript APIs unlike the AllSeen project. We > > >would like to fix that by introducing the JavaScript APIs for IoTivity > > >so developers can create web apps to participate the OIC ecosystem. Web > > >app in this context means both HTML5 and node applications. That is, we > > >would like to have one JS API available on multiple platforms. We are > > >targeting node (linux, win, OS X) and Android web applications in the > first phase. > > > > > >The foundation of the JS API is good API design. Please find the > > >attached .pdf the early draft of the API. Any feedback is welcome. The > > >author > > >(cc?d) of the API is currently on vacation but will address all the > > >feedback once he comes back online in few weeks. > > > > > >We are also publishing the node implementation of the API soon. We > > >would like to host the project under the IoTivity project. Perhaps > > >create a second repo at iotivity.org. Currently the repo is hosted at > GitHub. > > >Following the node implementation we will also publish the same API for > > >the Crosswalk for Android (https://crosswalk-project.org/). > > > > > >Feel free to ask any questions or raise concerns. > > > > > >Thanks, Sakari > > >Intel, Open Source Technology Center, Helsinki, Finland > > > > _______________________________________________ > > iotivity-dev mailing list > > iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
