From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30359 invoked by alias); 23 Nov 2003 21:54:31 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 30338 invoked from network); 23 Nov 2003 21:54:30 -0000 Received: from unknown (HELO garm.central.cmich.local) (141.209.15.48) by sources.redhat.com with SMTP; 23 Nov 2003 21:54:30 -0000 Received: from leon.phy.cmich.edu ([141.209.165.20]) by egate1.central.cmich.local with Microsoft SMTPSVC(5.0.2195.6713); Sun, 23 Nov 2003 16:54:23 -0500 Received: from localhost (unknown [127.0.0.1]) by leon.phy.cmich.edu (Postfix) with ESMTP id DE1C97001D; Sun, 23 Nov 2003 16:54:20 -0500 (EST) Date: Mon, 24 Nov 2003 00:26:00 -0000 From: Eric McDonald To: Hans Ronne Cc: xconq7@sources.redhat.com Subject: Re: Xconq output files In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 23 Nov 2003 21:54:23.0088 (UTC) FILETIME=[5AE5FF00:01C3B20C] X-SW-Source: 2003/txt/msg00912.txt.bz2 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