Doc team April/May report

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Doc team April/May report

Tapple Gao
I never sent a monthly report for the month of April, so this is
a two-month report.

In the March report, I promised, with the help of Paul Bennet,
that we would have a plan to get Seaside Documentation to a
better state by the end of the Month. Paul Bennet, however,
disappeared just as fast as he had appeared, so this never
happened. Also, I was very busy in April finishing my school
projects, so *nothing* happened April.

Around the beginning of May, I began discussing on #squeak what
kind of tools would make it easier for people to contribute to
Squeak Documentation. The consensus seems that successful
documentation for squeak would need to be as distributed,
navigable, and searchable as code for squeak. Seems reasonable.
Around mid-may, I was discussing this again, and Simon Michael
and Ken Causey said they would lend some unofficial help.
Within the last week, I started a small project to help me learn
Seaside and perhaps boost the amount of testing and discussion
that happens around Squeak code: adding email notification to
SqueakSource commits. It should be fun.

Also this month, I re-arranged the tutorial list I have been
building to be more navigable: http://wiki.squeak.org/squeak/792

I haven't really heard from Andrew Lawson about his Collections
tutorial, or from Aaron Riechow about his screencasts for three
months.

Suggestions are always welcome. Keep on Squeaking.

--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
Help improve Squeak Documentation: http://wiki.squeak.org/squeak/808

Reply | Threaded
Open this post in threaded view
|

Re: Doc team April/May report

K. K. Subramaniam
On Thursday 07 June 2007 6:36 am, Matthew Fulmer wrote:
> Also this month, I re-arranged the tutorial list I have been
> building to be more navigable: http://wiki.squeak.org/squeak/792
> ...
> Suggestions are always welcome. Keep on Squeaking.
When I started with Squeak, I got really frustrated with 'static'
documents/books that soon got dated, links that went nowhere and so on. The
terminology was cryptic with difficult to map metaphors. The break came when
I started using Squeak itself as a live document and started filing in code
snippets. 'debug it' was a godsend. Learning by exploring served my needs
very well. Experts, with their great one-liners, hastened the pace.

Squeak is very different from other systems which separate programming into
separate actions with separate tools. Squeak acts like a tightly integrated
computer. IMHO, bundling an image with 'how to' projects (like squeakland
projects) would the way to go. This could be supplemented by code snippets
that could be filed in and observed to learn programming. Squeakland's
glossary.pdf deserves far better than "0 google hits".

Regards .. Subbu