Re: Xconq output files

[Eric McDonald <mcdonald at phy dot cmich dot 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.

> * Warning files ("Xconq.Warnings" on all platforms).
> * Debug files ("Xconq.DebugOut" on all platforms).

"XconqWarnings.log" and "XconqDebugOut.log".

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

"XconqPrefs" or "XconqPrefs.txt".

> * Scores files ("scores.xcq" for most games, but some games have their own
> scores files).

"XconqScores" or "XconqScores.txt" for the main scores file.

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

"XconqStats"

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

"ErrorSave.xcq"

All files that do not have the ".xcq" extension are prefaced with 
"Xconq". This helps Xconq keep all of its files within a namespace 
and lessens the chance of colliding with other apps. The ".xcq" 
applies universally to anything that is a saved Xconq game.

Legacy support can be added to the code so that it will try 
reading a file called "prefs.xcq" if "XconqPrefs" does not exist 
yet.

Sound reasonable?

Eric