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
lcdoc & contributing to dictionary
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: lcdoc & contributing to dictionary
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
Where is the documentation for lcdoc format?
Livecode Wiki: http://livecode.wikia.com
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
Re: lcdoc & contributing to dictionary
Livecode Wiki: http://livecode.wikia.com
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w
My blog: https://livecode-blogger.blogspot.com
To post code use this: http://tinyurl.com/ogp6d5w