[dev] IoTivity documentation standards

2017-03-24 Thread 최우제 (Uze Choi)
From: JiHwan Seo [mailto:jihwan@samsung.com] Sent: Friday, March 24, 2017 3:55 PM To: Mats Wichmann; Uze Choi; ASHOKBABU CHANNA; 'Nash, George'; 'C.J. Collier' Cc: 'IoTivity Developer List' Subject: RE: Re: [dev] IoTivity documentation standards Hi Uze and Mats. Since there were so many

[dev] IoTivity documentation standards

2017-03-24 Thread JiHwan Seo
HTML ?? ??... URL: -- next part -- A non-text attachment was scrubbed... Name: ?? ?? . Type: image/gif Size: 13402 bytes Desc: ?? ?? .

[dev] IoTivity documentation standards

2017-03-23 Thread 최우제 (Uze Choi)
APIs. BR, Uze Choi From: Nash, George [mailto:george.n...@intel.com] Sent: Thursday, March 23, 2017 12:55 AM To: uzchoi at samsung.com; 'C.J. Collier'; 'Mats Wichmann' Cc: 'IoTivity Developer List' Subject: RE: [dev] IoTivity documentation standards Thanks Uze for taking the time to help figure

[dev] IoTivity documentation standards

2017-03-23 Thread Ashok Babu Channa
at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ??? (Uze Choi) Sent: Thursday, March 23, 2017 3:23 PM To: 'Nash, George'; 'C.J. Collier'; 'Mats Wichmann' Cc: 'IoTivity Developer List' Subject: Re: [dev] IoTivity documentation standards Hi Ashok, Can you check the connectivity

[dev] IoTivity documentation standards

2017-03-23 Thread Nash, George
ration for these special APIs. BR, Uze Choi From: Nash, George [mailto:george.n...@intel.com] Sent: Thursday, March 23, 2017 12:55 AM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com>; 'C.J. Collier'; 'Mats Wichmann' Cc: 'IoTivity Developer List' Subject: RE: [dev] IoTivity documentati

[dev] IoTivity documentation standards

2017-03-23 Thread 최우제
HTML ?? ??... URL: -- next part -- A non-text attachment was scrubbed... Name: ?? ?? . Type: image/gif Size: 13402 bytes Desc: ?? ?? .

[dev] IoTivity documentation standards

2017-03-23 Thread Mats Wichmann
On 03/23/2017 08:24 AM, ??? wrote: > Thanks Ashok. > Then cautilinterface.h also has lots of functions. > All are required open? This header has no @file section, is there a description of the purpose of the header available?

[dev] IoTivity documentation standards

2017-03-22 Thread Nash, George
rials"? If not I am sure I can come up with something. -Original Message- From: Mats Wichmann [mailto:m...@wichmann.us] Sent: Wednesday, March 22, 2017 9:07 AM To: Nash, George ; uzchoi at samsung.com; 'C.J. Collier' Cc: 'IoTivity Developer List' Subject: Re: [dev] IoTivity documentation

[dev] IoTivity documentation standards

2017-03-22 Thread Nash, George
' Subject: RE: [dev] IoTivity documentation standards I am happy to see meaningful discussion happen so I can expect improvement the doxygen documentation. Step by step, Let?s focus on the External C API first, C++ and Java in sequence. Think about the internal API as next step. Let me suggest

[dev] IoTivity documentation standards

2017-03-22 Thread 최우제 (Uze Choi)
Subject: Re: [dev] IoTivity documentation standards Mats, I am glad that you have brought up some of these issues. I disagree that the efficient doxygen comments page sounds mandatory. However, all of the suggestions probably are best to be followed. (a)Based on recent commits that I have

[dev] IoTivity documentation standards

2017-03-22 Thread Mats Wichmann
On 03/22/2017 10:30 AM, Nash, George wrote: > I was tempted to make the OPTIMIZE_OUTPUT_FOR_C change with my other commit. > I chose not to since I was not sure if there was a reason not to change it. Someone who's been on the project a long time would have to comment on the "not change"

[dev] IoTivity documentation standards

2017-03-22 Thread Mats Wichmann
On 03/22/2017 09:55 AM, Nash, George wrote: > Thanks Uze for taking the time to help figure out which header files are > intended for the public API: > > It looks like a few of the headers from your list differ from the list that > was in my recent commit

[dev] IoTivity documentation standards

2017-03-21 Thread Wouter van der Beek (wovander)
. Collier ; Mats Wichmann ; IoTivity Developer List Subject: Re: [dev] IoTivity documentation standards Wouter, Just out of curiosity.. This code generation tool you're working.. Is it public or private? regards, Thiago On Tue, Mar 21, 2017 at 12:01 PM, Wouter van der Beek (wovander

[dev] IoTivity documentation standards

2017-03-21 Thread Wouter van der Beek (wovander)
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Nash, George Sent: 20 March 2017 22:11 To: C.J. Collier ; Mats Wichmann Cc: IoTivity Developer List Subject: Re: [dev] IoTivity documentation standards Mats, I am glad that you have brought up some of these issues. I disagree

[dev] IoTivity documentation standards

2017-03-21 Thread Thiago Moura
outer > > > > *From:* iotivity-dev-bounces at lists.iotivity.org [mailto: > iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *Nash, George > *Sent:* 20 March 2017 22:11 > *To:* C.J. Collier ; Mats Wichmann < > mats at wichmann.us> > > *Cc:* IoTivity D

[dev] IoTivity documentation standards

2017-03-20 Thread Nash, George
...@lists.iotivity.org] On Behalf Of C.J. Collier Sent: Monday, March 20, 2017 1:50 PM To: Mats Wichmann Cc: IoTivity Developer List Subject: Re: [dev] IoTivity documentation standards Hello Mats, Having not participated in the documentation of the API to date, I am certainly not an authority

[dev] IoTivity documentation standards

2017-03-20 Thread C.J. Collier
Hello Mats, Having not participated in the documentation of the API to date, I am certainly not an authority on the matter. But I'll give my two cents anyway! First, the questions regarding wiki page contents might be best directed to Jon A. Cruz, the author of the wiki page. I've CC'd Jon so

[dev] IoTivity documentation standards

2017-03-20 Thread Mats Wichmann
Sorry if this seems to ramble a bit, there are several questions inline. We have a wiki page for doxygen markup in the source tree: https://wiki.iotivity.org/efficient_doxygen_comments Despite the title of the page ("efficient use"), it starts out sounding very "mandatory" (highlighting mine):