From: Max Techter <mtechter@gmx.de>
Cc: guile-devel@gnu.org
Subject: Re: Doc organization (Re: Around again, and docs lead role)
Date: 08 May 2003 23:12:54 +0200 [thread overview]
Message-ID: <86znlxdtwp.fsf@520000401788.dialin.t-online.de> (raw)
In-Reply-To: <3EB9828B00021495@pop1.tiscalinet.es> (added by postmaster@netmail.tiscalinet.es)
Ricard Mira <ricardmm@tiscali.es> writes:
> Max Techter wrote:
> > What about a tutorial, Ricard?
>
> There is already a Guile tutorial, but it's quite incomplete. On the
> other hand, it seems that most of the material in parts I, II and III
> of the Guile reference manual are introductory.
>
I agree on this.
But IMHO a tutorial and an introduction is
definitely not an exclusive alternative.
> I guess it's not clear yet whether Guile should have a separate
> tutorial, or an introductory section (or some introductory sections)
> in the reference manual.
>
Sure.
Anyway, keeping a tutorial separated
and on a different level(*)
is a good idea.
(Same principle as in python documentation).
(*) concerning what you suppose about the knowledge of
the audience, you are aiming at; concerning what you
want to communicate,...
If you keep the tutorial (which) should be
practical, the whirlwind tour should be theoretical.
Introductory stuff should be kept formal.
Tutorial may be informal, if necessary even
a little bit unprecise, but it has to get you going
immediately.
We should not bother too much about the structure
already there, if it is clear that there has to be
done some restructuring.
There are well known
principles how to document a system.
( And a standalone- (python),
or integrated-tutorial (bison) is a good ingredient for
the doc of every non trivial system) ;-)
The problem is not so much in finding a suitable
structure but in writing and maintaining, without
washing the structure away again.
Keeping the proportions is a problem too, but
we do not have to bother about this, now.
(
The work already done, is a fine prototype.
We may infer the structure needed, from the
problems this documentation posed.
).
Maybe I underestimate the complexity, of the needed
guile documentation.
I`ll try to work out a proposal.
I am engaged in scheme and guile anyway,
and this will force me to have a structured go.
(Guess I`ll need =< a fortnight)
regards
max.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-08 21:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 7:33 Around again, and docs lead role Neil Jerram
2003-04-26 10:19 ` Thamer Al-Harbash
2003-04-27 20:56 ` Neil Jerram
[not found] ` <3E92E1B40021F4D7@pop3.tiscalinet.es>
2003-04-27 21:01 ` Neil Jerram
[not found] ` <3E92E1B4002B0632@pop3.tiscalinet.es>
2003-04-30 22:47 ` Neil Jerram
[not found] ` <3EAFE4EC000D9733@pop1.tiscalinet.es>
2003-05-07 21:06 ` Doc organization (Re: Around again, and docs lead role) Neil Jerram
2003-05-08 16:21 ` Rob Browning
2003-05-08 17:50 ` rm
2003-05-08 22:47 ` Neil Jerram
2003-05-08 21:18 ` Wolfgang Jaehrling
2003-05-08 22:36 ` Neil Jerram
2003-05-09 2:23 ` Rob Browning
2003-05-09 17:46 ` David Van Horn
2003-05-10 11:32 ` Neil Jerram
2003-05-15 16:02 ` Rob Browning
2003-05-15 16:33 ` Paul Jarc
2003-05-08 16:21 ` Max Techter
[not found] ` <3EB9828B00021495@pop1.tiscalinet.es>
2003-05-08 21:12 ` Max Techter [this message]
2003-05-27 2:02 ` Max Techter
2003-05-08 22:57 ` Neil Jerram
2003-05-09 12:32 ` Max Techter
2003-05-09 8:15 ` tomas
2003-05-10 12:01 ` Neil Jerram
2003-05-12 11:40 ` tomas
2003-05-12 16:46 ` Around again, and docs lead role Max Techter
2003-05-12 20:25 ` Neil Jerram
2003-05-13 14:14 ` Max Techter
2003-05-13 19:56 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86znlxdtwp.fsf@520000401788.dialin.t-online.de \
--to=mtechter@gmx.de \
--cc=guile-devel@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).