From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Elijah Meeks <elijahmeeks@yahoo.com>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: Publicity Test Run
Date: Sun, 14 Nov 2004 00:54:00 -0000 [thread overview]
Message-ID: <41969ED8.5060904@phy.cmich.edu> (raw)
In-Reply-To: <1100388220.15874.77.camel@localhost>
Lincoln Peters wrote:
> Perhaps a better system for categorizing games, both by genre and
> development stage, would go a long way here. Something like this
> updated version of my proposed GTK+-based "Welcome" screen (which could
> be mimicked to the same effect with TclTk or ParaGUI):
>
> http://homepage.mac.com/lmpeters/welcome2.png
Yes. I had some very, very similar thoughts a couple of weeks ago. I had
intended to quietly introduce such a system when I was creating the
SDL/ParaGUI setup screens.
For the most part I agree with your storyboard. I would suggest that
"SciFi/Fantasy" be broken up into two separate genres: "Fantasy" and
"SciFi", and that another genre, "Miscellaneous", be added. The Insects
game would likely fall into that category.
Also, I think that with the "Development" checkboxes, the "Show
unfinished games" checkbox is no longer necessary. Indeed, finding a way
to get rid of that checkbox or something similar is what led me to think
of the classification system which you have also arrived at. I am not
very comfortable with the word "unfinished" in the context of Xconq,
since it does not necessarily mean incomplete development.
The historical genres might benefit from being renamed to things like
"Stone and Bronze Age Warfare", "Iron Age Warfare", "Gunpowder Age
Warfare", "Industrial Age Warfare", and "Modern Age Warfare". Another
genre might be needed to cover Advances or Civ2 like games where a
progression through multiple ages is possible.
Just my two cents,
Eric
P.S. The way I had previously been considering prior to this
classification system was to break the Xconq library up into a number of
sublibraries, and then setup navigation to the different games
libraries. However, this creates a problem for games that may belong to
more than one genre.
next prev parent reply other threads:[~2004-11-13 23:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 23:28 SDL Interface Development Eric McDonald
2004-10-31 4:10 ` Lincoln Peters
2004-10-31 6:13 ` Eric McDonald
2004-10-31 6:34 ` Elijah Meeks
2004-10-31 7:34 ` Lincoln Peters
2004-10-31 18:39 ` Eric McDonald
2004-10-31 18:23 ` Eric McDonald
2004-10-31 6:54 ` D. Cooper Stevenson
2004-10-31 18:26 ` Eric McDonald
2004-10-31 16:28 ` Skeezics Boondoggle
2004-10-31 19:04 ` Eric McDonald
2004-10-31 19:04 ` Lincoln Peters
2004-10-31 19:50 ` Skeezics Boondoggle
2004-11-07 8:29 ` Publicity Test Run Elijah Meeks
2004-11-13 23:23 ` New Source Tarball and Windows Installer (was Re: Publicity Test Run) Eric McDonald
2004-11-13 23:55 ` Publicity Test Run Lincoln Peters
2004-11-14 0:54 ` Eric McDonald [this message]
2004-11-14 22:31 ` Lincoln Peters
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=41969ED8.5060904@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=sampln@sbcglobal.net \
--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).