public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: New Documentation: Games Library
Date: Mon, 26 Jul 2004 18:32:00 -0000	[thread overview]
Message-ID: <4104F4B3.4070207@phy.cmich.edu> (raw)
In-Reply-To: <200407260530.i6Q5UE316566@panix5.panix.com>

Jim Kingdon wrote:


> Ah, OK, so that's what all that help system hacking was all about.

Yeah, you didn't really think I was doing nothing and just writing up 
changelog entries for it, did you? :-)

> * Provide some brief introductory text at the top of the "Table of
> Contents" page.  Perhaps the existing string which is "The standard
> Xconq game, loosely based on WW II ca 1945." in the case of standard.g.

This sounds reasonable.

> * Images for units, terrain, etc.

I had that in mind as a longer term goal. It would probably be nice to 
convert the associated images to PNG's or something.

> * General cosmetic improvements.

To the help file output or to the help system in general? If you're 
referring to the help system in general, that is something I am going to 
continue to wittle away at (as mentioned in my previous message). If you 
want to see cosmetic improvements that I have already made, then the 
first couple of paragraphs of the unit type descriptions are an example 
of what I have in mind. Even those can be further improved; I plan on 
making list (table row or table col) output easier to read, and making 
subsection headings stand out better (probably with an H4 tag in HTML).

Eric

  reply	other threads:[~2004-07-26 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26  5:30 Eric McDonald
2004-07-26 12:11 ` Jim Kingdon
2004-07-26 18:32   ` Eric McDonald [this message]
2004-07-26 19:09     ` Hans Ronne
2004-07-28 17:14       ` 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=4104F4B3.4070207@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).