From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Xconq output files
Date: Mon, 24 Nov 2003 00:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311231605130.14360-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130301bbe6c1c17025@[212.181.162.155]>
On Sun, 23 Nov 2003, Hans Ronne wrote:
> >I vote to leave saved games with ".xcq". Furthermore, I would
> >like to change the checkpoint savefiles to ".xcq" as well, since
> >they really are saved Xconq games.
>
> Yes. It makes sense for all game files to end in .xcq, so that they are
> opened by Xconq. I even contemplated if all the .g files should be renamed
> .xcq, but that would go to far (and also break the CVS record for all the
I thought about this as well, which is why I made sure to mention
the word "save".
I could also associate ".g" with xconq.exe. But here I am a
little bit more concerned with clobbering an existing extension.
I think I can incorporate logic into the installer script to
check for this though.
> >"XconqWarnings.log" and "XconqDebugOut.log".
>
> Not sure about this one. A .log file to me is something that accumulates
> output from several sessions. Which these files do not. How about just
> XconqWarnings?
Sure, or how about "XconqWarnings.xcd" as you suggest below, but
only for Windows? Since the default view settings in Windows
Explorer hide file extensions, the ".xcd" files will appear to
have the same names as they do on other platforms, but I will be
able to associate shell extensions (e.g., Open) with them. (And
for people like me, who prefer to see the extensions when dealing
with Windows, they will appear less "clumsy".)
> >"XconqPrefs" or "XconqPrefs.txt".
>
> I like XconqPrefs. The .txt extension looks screwy except on Windows where
I'll do XconqPrefs.xcd on Windows unless you object.
> Alternatively, we could have a second unique extension (.xcd ?) for all
> Xconq-related doc files that should be opened in a text editor. Perhaps
> this is a better idea.
>
> >"XconqScores" or "XconqScores.txt" for the main scores file.
>
> XconqScores is fine. However, since different games make different score
> files, this is a tricky one.
Well, we could alter existing modules where 'scorefile-name' is
set to conform to some naming standard (perhaps the name of the
the game module file minus the ".g" extension; in which case
Bellum would be the only game currently in the library that needs
to change). I would suggest that we remove any extensions from
these, and then let the Xconq Windows code tack on a ".xcd".
So how does this sound?
Eric
next prev parent reply other threads:[~2003-11-23 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 21:47 Hans Ronne
2003-10-06 2:24 ` Peter Garrone
2003-10-06 3:42 ` Jim Kingdon
2003-10-07 3:28 ` Hans Ronne
2003-10-06 22:04 ` Eric McDonald
2003-11-23 20:12 ` Eric McDonald
2003-11-23 21:54 ` Hans Ronne
2003-11-24 0:26 ` Eric McDonald [this message]
2003-11-26 21:53 ` Hans Ronne
2003-11-26 22:56 ` Eric McDonald
2003-12-01 1:38 ` Hans Ronne
2003-11-24 1:25 ` Xconq testing: Win2K Erik Jessen
2003-11-24 2:16 ` Hans Ronne
2003-11-24 2:27 ` Erik Jessen
2003-11-25 1:47 ` Hans Ronne
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.0311231605130.14360-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@comhem.se \
--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).