lcdoc & contributing to dictionary
Posted: Fri Aug 21, 2015 3:11 am
Hi,
I've written a little script to create a Dash app "docset" as I noticed there wasn't already one ..anyway ... I didn't know what Livecode documentation to base it on—I can see 3 different types of livecode documentation: XML, lcdoc, and in LC8 I see json (locally installed, not on github).
I used the lcdoc—is that the most sensible choice going forward? Is there a spec for it? I recall seeing a blog post on livecode about the doco format changing, and lcdoc was proposed (suggesting XML deprecated) but I don't think it was finalised?
So ... if i wanted to help fix some documentation problems (formatting, typos, add examples, etc) what files am i forking and making pull requests on in github? the lcdocs?
thanks for any help
- mark
I've written a little script to create a Dash app "docset" as I noticed there wasn't already one ..anyway ... I didn't know what Livecode documentation to base it on—I can see 3 different types of livecode documentation: XML, lcdoc, and in LC8 I see json (locally installed, not on github).
I used the lcdoc—is that the most sensible choice going forward? Is there a spec for it? I recall seeing a blog post on livecode about the doco format changing, and lcdoc was proposed (suggesting XML deprecated) but I don't think it was finalised?
So ... if i wanted to help fix some documentation problems (formatting, typos, add examples, etc) what files am i forking and making pull requests on in github? the lcdocs?
thanks for any help
- mark