Page 1 of 1

lcdoc & contributing to dictionary

Posted: Fri Aug 21, 2015 3:11 am
by scrabbles
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

Re: lcdoc & contributing to dictionary

Posted: Tue Aug 25, 2015 12:22 pm
by scrabbles
Just to answer my own questions in case it benefits others:
  • - lcdoc does seem to be the format going forward in v8 (I am unsure if changes get back ported to 6x though, i think they do for 7.1)
    - The LCv8 dictionary (open it in livecode) has a guide tab, which has a specifications section explaining the lcdoc format.
    - Pull requests (on github) can be made for (signed up) contributors. The lcdocs are fine to edit and submit PRs for.

Re: lcdoc & contributing to dictionary

Posted: Wed Jan 20, 2016 10:30 am
by MaxV
Where is the documentation for lcdoc format?

Re: lcdoc & contributing to dictionary

Posted: Wed Jan 20, 2016 10:40 am
by bn

Re: lcdoc & contributing to dictionary

Posted: Wed Jan 20, 2016 11:09 am
by MaxV