9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anant Narayanan <anant@kix.in>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Suggestion: Programming Tutorial for /sys/doc
Date: Sat,  3 Nov 2007 00:42:17 +0530	[thread overview]
Message-ID: <472B7691.4010807@kix.in> (raw)
In-Reply-To: <02597431-3833-4DDD-8720-E0B2761DBE88@mac.com>

Pietro Gagliardi wrote:
> cover in a clear way, so I think a tutorial should be put in. I already
> started writing one, and I think it would benefit from being in
>     - graphics and controls

While I am mostly able understand the other concepts you mention from
existing documentation, I find graphics (libdraw) to be somewhat
cryptic. I've always felt the need for a tutorial-style introduction on
how to do graphics in Plan 9.

The current solution seems to be mostly be: "Read the code". Which isn't
really as good.

Uriel wrote:
> Just thinking out loud here so I might make no sense, but I suspect
> the issue is that the style of the plan9 documentation is very
> different from what people have become used to expect, this days
> people expects 'tutorials' and other handholding with many examples to
> 'copy paste' into their code and so on, which is quite different from
> the Unix/Plan 9 documentation style of clear and concise information
> and simple examples that help illustrate the general concepts, but
> that does require the reader to actually *understand* things rather
> than just follow an arbitrary set of steps.

Sometimes people need hand-holding, especially when they're trying to
learn a completely new system. I am all for conventional tutorial-style
introductions to Plan 9.

Even if the tutorial shamelessly repeats a lot (all?) of the information
in the man pages and papers, redundancy in documentation never really
hurt anyone. In fact, the more, the merrier :)

Cheers,
--
Anant


  parent reply	other threads:[~2007-11-02 19:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 20:11 Pietro Gagliardi
2007-11-01 20:23 ` don bailey
2007-11-01 20:47 ` Anthony Sorace
2007-11-01 21:00   ` Pietro Gagliardi
2007-11-01 21:22     ` Federico Benavento
2007-11-02 13:10       ` Iruata Souza
2007-11-02 13:34         ` David Leimbach
2007-11-02 13:39           ` erik quanstrom
2007-11-02 16:44             ` geoff
2007-11-02 18:00               ` erik quanstrom
2007-11-02 19:34                 ` geoff
2007-11-02 20:57                   ` David Leimbach
2007-11-03  2:44                 ` Gorka Guardiola
2007-11-03  8:49                   ` Sander van Dijk
2007-11-03 15:24                     ` Eldanen
2007-11-03 21:43                       ` erik quanstrom
2007-11-03 23:40                         ` Eldanen
2007-11-06 14:39                         ` [9fans] Font Michaelian Ennis
2007-11-06 14:46                           ` Anant Narayanan
2007-11-06 14:50                             ` erik quanstrom
2007-11-07 18:12                               ` Michaelian Ennis
2007-11-06 14:56                           ` Martin Neubauer
2007-11-05 11:59                     ` [9fans] Suggestion: Programming Tutorial for /sys/doc Gorka Guardiola
2007-11-02 18:09             ` David Leimbach
2007-11-02 18:47         ` Pietro Gagliardi
2007-11-02 20:11           ` Iruata Souza
2007-11-02 18:52         ` Pietro Gagliardi
2007-11-01 21:27     ` Uriel
2007-11-02  1:44     ` Anthony Sorace
2007-11-02  7:53       ` Uriel
2007-11-01 21:24 ` ISHWAR RATTAN
2007-11-02  3:07 ` Joel C. Salomon
2007-11-02  8:19 ` fernanbolando
2007-11-02 10:03   ` roger peppe
2007-11-02 13:07     ` Eric Van Hensbergen
2007-11-02 12:42   ` erik quanstrom
2007-11-02 15:39 ` Douglas A. Gwyn
2007-11-02 19:12 ` Anant Narayanan [this message]
2007-11-02 19:44   ` Pietro Gagliardi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=472B7691.4010807@kix.in \
    --to=anant@kix.in \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).