Author: Michael Yee
Date: 05:07:00 03/19/05
Go up one level in this thread
Hi Dann, Just to make sure I'm picturing the use of your database correctly... Is this similar to what you had in mind? - person has several chess GUIs or other programs on their system - person has your database system installed - say a new engine comes out - they "install" the engine *once* by registering it with your database - then all GUIs that support the database can simply treat the new engine as one of *its* installed engines, too - if GUI creates a new parameter "personality" or whatever, it can save it in the database (which makes it available to other GUIs, too) To support this kind of use, it seems like the database system would need a front end to manage installation. (Or maybe any of the GUIs could function as this front end.) And maybe some other data needs to be stored like path to executable, path to logo file, protocols supported, etc.? In other words, should the database include all data necessary for a GUI to be able to run and customize the engine? Michael
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.