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: Xconq output files
Date: Sun, 23 Nov 2003 21:54:00 -0000	[thread overview]
Message-ID: <l03130301bbe6c1c17025@[212.181.162.155]> (raw)
In-Reply-To: <Pine.LNX.4.44.0311231430450.14360-100000@leon.phy.cmich.edu>

>We never really got resolution on this thread. Since ".xcq" is now
>associated with Xconq on the Windows platform, I would like to
>clear things up.
>
>On Sun, 5 Oct 2003, Hans Ronne wrote:
>
>> I've been looking at the various files that Xconq creates recently, since I
>> have been fixing a number of MacOSX-related problems involving these files.
>> Anyhow, this got me thinking. A plethora of files are created by Xconq.
>> Furthermore, their names and locations vary according to the platform, the
>> interface, and the game being played:
>>
>> * Saved game files ("save.xcq" on Unix and Windows, "Saved Game" on the
>>Mac).
>> * Checkpoint files ("checkNN.xconq" on Unix and Windows, "Checkpoint" on
>> the Mac).
>
>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
game files). I already started to implement some of these changes on the
Mac.

>> * Warning files ("Xconq.Warnings" on all platforms).
>> * Debug files ("Xconq.DebugOut" on all platforms).
>
>"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?

>> * Preference files ("prefs.xcq" in the tcltk interface, "Xconq Preferences"
>> in the PPC interface).
>
>"XconqPrefs" or "XconqPrefs.txt".

I like XconqPrefs. The .txt extension looks screwy except on Windows where
it is invisible. Of course, it is there that it is needed the most. Since
we want all these files to open in a text editor, is it possible to tell
Windows that anything that starts with Xconq should be openend in a text
editor?

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.

>> * Scores files ("scores.xcq" for most games, but some games have their own
>> scores files).
>
>"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.

>> * Statistics files ("stats.txt" on Unix and Windows, "Statistics" on the
>>Mac).
>
>"XconqStats"

Yep.

>> * Error files ("ERRsave.xcq" on Unix and Windows, "Error Save" on the Mac).
>
>"ErrorSave.xcq"

Yep.

Hans


  reply	other threads:[~2003-11-23 20:12 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 [this message]
2003-11-24  0:26     ` Eric McDonald
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='l03130301bbe6c1c17025@[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).