public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: New Documentation: Games Library
Date: Mon, 26 Jul 2004 19:09:00 -0000	[thread overview]
Message-ID: <l03130301bd2afbd96cbd@[212.181.162.155]> (raw)
In-Reply-To: <4104F4B3.4070207@phy.cmich.edu>

>> * 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.

This is a very nice addition. Hopefully, it will make people browsing the
web site more interested in trying out the game.

I have two suggestions.

One is what Jim already asked for, even though he didn't refer to it by
name: the blurb. This is the most important item in the whole help system,
since it provides a brief description of the game. Only some games have
instructions, but every one has a blurb that makes sense. I made sure about
that when I updated the game library earlier this year. The blurb can now
also be much longer (max 480 characters) and I tweaked the interfaces so
that a bigger blurb can be displayed. So it is possible to put a little
more info in there than just the title and the author name.

The other thing that would be nice in the help pages are screenshots of the
games. Like the ones Stan already put on the web site a long time ago. This
would give the reader a much better idea about the available modules. Of
course, this would require some human work since I doubt that xcscribe
could be made to play games and take screenshots :-).

Hans




  reply	other threads:[~2004-07-26 18:32 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
2004-07-26 19:09     ` Hans Ronne [this message]
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='l03130301bd2afbd96cbd@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --cc=mcdonald@phy.cmich.edu \
    --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).