public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: xconq7@sources.redhat.com
Subject: Re: does the tutorial lie?
Date: Fri, 28 May 2004 06:45:00 -0000	[thread overview]
Message-ID: <200405280645.i4S6jKr07313@panix5.panix.com> (raw)
In-Reply-To: <1085709882.1485.553.camel@localhost.localdomain> (message from Eric McDonald on Thu, 27 May 2004 20:04:42 -0600)

> I think a valid question is: should they be marked as such on the Xconq
> Web site? These manuals also do contain up-to-date information, so maybe
> they should simply have a caveat lector note next to their links.

I suppose some kind of disclaimer would be OK, although of course it
might just lead to general doubt and uncertainty rather than critical
reading.

I'd like to see us do at least *something* about inaccuracies as we
notice them.  Towards that end, I checked in a change to the example
in the tutorial which at least notes the ZOC issue, even though I
didn't take the time to really try out the example and figure out how
much it matches current reality.  (Not to mention think about the
teaching order as a tutorial and whether there is a better way to
demonstrate unit-size-in-terrain without getting bogged down in ZOC
which is a more advanced feature, as the default ZOC behavior is
adequate for many games.  But I'm saying that a note is a good first
step which we can do even before that kind of full update happens).

  reply	other threads:[~2004-05-28  6:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 23:55 Tom Schaub
2004-05-28  0:37 ` Stan Shebs
2004-05-28  0:47 ` mskala
2004-05-28  2:07   ` Eric McDonald
2004-05-28  6:45     ` Jim Kingdon [this message]
2004-05-28 16:46       ` Eric McDonald
2004-05-28 17:46       ` Stan Shebs
2004-05-28 17:27     ` Stan Shebs
2004-05-29  1:20       ` Eric McDonald

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=200405280645.i4S6jKr07313@panix5.panix.com \
    --to=kingdon@panix.com \
    --cc=xconq7@sources.redhat.com \
    /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).