First, thanks to everybody who replied to my requests on Python,
Smalltalk, and FORTH documentation tools. I will put the links you
have given me into the document outlines linked from the OLPC
Publications page, and at some point we can start expanding the
outlines into draft documents. Further
On Jan 1, 2008 3:14 PM, M. Edward (Ed) Borasky [EMAIL PROTECTED] wrote:
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
Are you looking for automated documentation generation, or FORTH coding
On Dec 30, 2007 10:20 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
I have run the python documentation tool 'epydoc' on the contents of
the joyride-1477 release. The results are here:
http://dev.laptop.org/~cscott/joyride-1477-api/
Thanks. I was wishing for that. Can you do the other
Sorry. It got away from me.
On Jan 1, 2008 2:11 PM, Edward Cherlin [EMAIL PROTECTED] wrote:
On Dec 30, 2007 10:20 AM, C. Scott Ananian [EMAIL PROTECTED] wrote:
I have run the python documentation tool 'epydoc' on the contents of
the joyride-1477 release. The results are here:
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
Are you looking for automated documentation generation, or FORTH coding
and documentation standards? I don't know about the former, but there is
a
From: Edward Cherlin [EMAIL PROTECTED]
And what about Smalltalk/Etoys?
Not sure what level of doc you're seeking. If I misunderstood you, I
apologize.
Smalltalk's libraries are to a certain extent self-documenting in its
browser, which is good because they vary depending on whatever you've
Edward Cherlin wrote:
Does anybody know of a documentation tool for Open Firmware, or for
FORTH more generally? Exploring using 'words' and 'see'
is fun up to a point if you're learning FORTH, but really doesn't cut
it for supporting documentation.
I presume that you have seen
On Dec 30, 2007 1:31 PM, Jeffrey Kesselman [EMAIL PROTECTED] wrote:
In general it would be good if a docs could be made downloadable... I
don't always have net access.
Good point. When I integrate this into the build process, I'll be
sure to .zip up the files as well.
In the interim:
