From: Andy Wingo <wingo@pobox.com>
To: Daniel Kraft <d@domob.eu>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Updated Guile Tutorial
Date: Thu, 13 Aug 2009 00:27:40 +0200 [thread overview]
Message-ID: <m3ljlollb7.fsf@pobox.com> (raw)
In-Reply-To: <4A7B223E.6050501@domob.eu> (Daniel Kraft's message of "Thu, 06 Aug 2009 20:34:38 +0200")
On Thu 06 Aug 2009 20:34, Daniel Kraft <d@domob.eu> writes:
> the last days, I worked on a rewrite of the Guile Tutorial (with the
> Tortoise package); just for fun, but also to update some stuff to my
> liking and last but not least change the API usage from the deprecated
> GH routines to the current scm_ ones.
This is great work. Thanks for bringing our tutorial up to date! I just
looked over the existing tutorial, and wow, anything that mentions Lotus
1-2-3, and fvwm...
A few comments, IMO of course. Neil probably has a better perspective.
1) It would be better to have a more neutral narrator -- not a
first-person narrator. If you feel like you need to speak from the
first person, use "we". OTOH your style is infectious :), so perhaps
it would work as "Guile Tutorial, by Daniel Kraft" :)
2) Don't mention the history of the tutorial. Just have it be a current
document.
3) In general, use short sentences. Let your words breathe.
4) If you're forking to run gnuplot, why not do so from Scheme? Of
course if you did that it would obviate the whole "extending C"
story, but still, if given this particular problem, that's what I'd
do.
5) Running a main loop (as gtk+ does) and a REPL is indeed an
interesting problem. See event-repl.scm or graphical-repl.scm in
guile-gnome for a couple of takes.
6) I wish we had a better Scheme->C story; our C->Scheme story is fine,
but a better FFI would be nice.
Anyway, IMO, FWIW, etc. If you don't reply, I'll probably just commit
your tutorial more-or-less as-is to the repo :)
A
--
http://wingolog.org/
next prev parent reply other threads:[~2009-08-12 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 18:34 Updated Guile Tutorial Daniel Kraft
2009-08-12 22:27 ` Andy Wingo [this message]
2009-08-13 7:43 ` Daniel Kraft
2009-08-24 15:39 ` Daniel Kraft
2009-09-20 16:35 ` Neil Jerram
2009-09-20 20:31 ` Daniel Kraft
2010-08-19 5:41 ` Andy Wingo
2010-08-21 14:38 ` Daniel Kraft
2010-08-28 18:46 ` Andy Wingo
2009-09-20 16:42 ` Neil Jerram
2009-09-20 17:17 ` Chris Bryant
2009-09-20 21:13 ` Neil Jerram
2009-09-20 17:18 ` Chris Bryant
-- strict thread matches above, loose matches on Subject: below --
2010-09-07 13:17 Daniel Kraft
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=m3ljlollb7.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=d@domob.eu \
--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).