From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: [OFFTOPIC?] Doc Chow (was Re: Windows Installer for Xconq)
Date: Mon, 03 Nov 2003 21:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311031604480.21403-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <200311032014.hA3KEHu25869@panix5.panix.com>
On Mon, 3 Nov 2003, Jim Kingdon wrote:
> I guess that makes sense. Imfapp is half a mebibyte on my linux
> system, and full sources seem to be about 5 mebibytes or so. Having
I think I can get used to saying "mebibyte", but "kibibytes"
really sounds like a brand of dog chow. Thankfully, a half a
kibibyte (aka, binary kilobyte) is not known as a "kibble", in the
way that half a byte is known as a "nibble". Otherwise, we would
have all these Kibbles and Bits floating around.
> the xconq sources are kind of useful in understanding how the game
> works until/unless we get more documentation volunteers than we have
> now.
Yes. Absolutely agreed.
If my motivation capacitor ever becomes sufficiently recharged
(wrt documentation), I intend to mention the formulae used by
each of the combat models for determining hits and misses and
damage. Another good thing that could be done, imo, is using
@ifhtml in the .texi sources, so that newer texi2html translators
can include raw HTML (useful for including screenshots in the
HTML versions of the docs).
I still need to write up some things regarding compound terrain
effects, but have been holding back because I think I should
refine that code further to deal with my previously mentioned
ideas about border and connector aux terains.
> I'd call the options something like "Normal" (everything you need to
> play xconq), "Designer" (includes files recommended for game
> designers), and "Source" (includes xconq source code, for those
> desiring maximum insight into xconq's functioning).
I'll consider what you suggest.
It's a dog's world,
Eric
next prev parent reply other threads:[~2003-11-03 21:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 8:32 Windows Installer for Xconq Eric McDonald
2003-11-03 17:27 ` Hans Ronne
2003-11-03 18:09 ` Eric McDonald
2003-11-03 20:14 ` Hans Ronne
2003-11-03 21:21 ` Jim Kingdon
2003-11-03 21:42 ` Eric McDonald [this message]
2003-11-04 6:45 ` Eric McDonald
2003-11-04 13:43 ` Hans Ronne
2003-11-04 16:37 ` Eric McDonald
2003-11-04 19:07 ` Hans Ronne
2003-11-04 20:03 ` Brandon J. Van Every
2003-11-04 21:25 ` Hans Ronne
2003-11-04 21:36 ` Brandon J. Van Every
2003-11-04 23:24 ` Brandon J. Van Every
2003-11-05 4:38 ` Hans Ronne
2003-11-05 8:54 ` Brandon J. Van Every
2003-11-06 5:23 ` Hans Ronne
2003-11-07 0:57 ` 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=Pine.LNX.4.44.0311031604480.21403-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=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).