Author: Roy Eassa
Date: 07:05:01 04/17/02
Go up one level in this thread
On April 17, 2002 at 09:30:48, Allen Lake wrote: >On April 17, 2002 at 08:53:04, Roy Eassa wrote: > >> >>That's the kind of stuff I was afraid of, using VB. >> >>If you follow the instructions on this site, does that help? : >> >>http://www.ascentive.com/cgi-bin/click/murfman39/support/2124DownloadList.html >> >>(I just did a google.com search on the file and the first site in the results >>seemed to offer a solution.) >> > >Once you have a copy of the DLL, the instructions on the site are okay, but >actually downloading the DLL was a problem (the web server didn't realize that >the DLL was a binary file and wanted to send it to me as html). I was able to >find the DLL in a zip archive on another site listed by Google, though. > >Have you abandoned the idea of doing a TCL version of Chesty? I have not abandoned re-doing it in Tcl/Tk. The DLL problems people are apparently having now raises the priority of doing it in SOMETHING that does not require any special DLLs (DLLs are the bane of my existence; Microsoft even started using them in their Mac apps, where DLLs previously did not exist!). Here's a copy of the current list of to-do's: Chesty future plans (not prioritized here) ------------------------------------------ 1. Figure out why a batch file is required (without it, Chest quits before you can read what it has to say) and do away with it if possible! 2. Show Chest's output in a separate, scrollable, GUI window. (Can be done by having Chesty pipe Chest's output to a file and, when Chest is finished, having the batch file invoke another [new] GUI app to display the contents of that file.) 3. Show progress / status while Chest is running (maybe by having Chesty "poll" a file that's the piped output from Chest, filtering it appropriately). 4. Permit the user to set additional parameters. Which ones? Feedback appreciated. 5. Rewrite in C (should be easy) or, better, in Tcl/Tk so it can be cross-platform. 6. Add a Windows icon, a Version resource, some help, etc. 7. Permit the user to point to (via a standard Open dialog box) the copy of Chest he wishes to use, rather than requiring that Chest be in the same directory as Chesty and be named "Chest.exe". 8. Save preferences in the registry (or maybe in a simple prefs file), especially for the location and name of Chest. 9. Give it a better name? Suggestions so far include the following: ChestCold, Chesterfield, WinChester, ChestCavity, TreasureChest, ChestMate, Orchestra, ChestRunner, RunChest. -Roy.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.