From: Lincoln Peters <sampln@sbcglobal.net>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: SDL/ParaGUI Development Progress
Date: Tue, 16 Nov 2004 01:06:00 -0000 [thread overview]
Message-ID: <1100549795.15874.8843.camel@localhost> (raw)
In-Reply-To: <4197DCB3.7090707@phy.cmich.edu>
On Sun, 2004-11-14 at 14:31, Eric McDonald wrote:
> Those wishing to make their own themes might do
> well to take a look at these files. The XML files in the 'paragui-tests'
> directory describe screen layouts. ParaGUI can read these layouts to
> automatically set up screens. Of course, the screens can also be
> generated line-by-line from code. (Technical note: ParaGUI uses an Expat
> implementation to parse the XML files.)
Does this mean that ParaGUI would be able to use different themes
depending on which game is being used? I seem to remember something
like that being discussed earlier, but until now it seemed like it would
be a lot of work to implement.
In fact, it might even get easier to implement if a system of game
categorization like the one I described yesterday was implemented, as it
sounds like you could have a different default theme for each genre,
while still allowing a game designer to optionally declare a specific
theme for a particular game!
Of course, I think we'll all agree that it's too early to worry about
such things.
---
Lincoln Peters
<sampln@sbcglobal.net>
Old age is always fifteen years old than I am.
-- B. Baruch
next prev parent reply other threads:[~2004-11-15 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:16 Eric McDonald
2004-11-16 1:06 ` Lincoln Peters [this message]
2004-11-16 3:02 ` 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=1100549795.15874.8843.camel@localhost \
--to=sampln@sbcglobal.net \
--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).