Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Crafty and assembly code

Author: A. Zanchetta

Date: 10:20:48 05/08/05

Go up one level in this thread


Hello Pedro,

On May 08, 2005 at 12:47:24, Pedro Castro wrote:

>Hello Alain,
>
>you are thinking the possibility that CEboard is for pokect PC what winboard is
>for PC?
>
>I talk about a system where the authors of other compatible programs xboard can
>make play their engines. It would not be even necessary that the sources of
>CEboard were opened.
>
>Is necessary to make many changes to porter a Winboard engine for PDA?, I
>believe that no, but I do not have nor idea where to find information, my
>program without hardly changes compiled for PDA, but not play. I previously have
>seen Pocket Crafty, even the sources, but the Crafty engine for my is too
>complicated to follow.
>
>It could have rules to change any engine to the format for PDA?
>
>Best wishes,
>
>Pedro

I have separated CEBoard and Crafty but did not go far enough to make CEBoard a
winboard like host : Pocket PC does not have the notion of standard input &
output and I prefered to host everything in one unique process.

The communication between CEBoard and Crafty is made via pure virtual classes
(in fact defined like COM interfaces except that they don't derive from
IUnknown) which are independant of Crafty and should be usable for other
engines.

So there is one big (not huge) file which I have integrated into Crafty's DLL
and which is Pocket PC specific :
- it handles the user interface of crafty (I wanted to expose all Crafty's
features through the UI and not via a configuration file)
- it converts the interface's functions into text commands which are
read/written by crafty the usual way (I almost inserted no code into crafty's
core)

Porting another engine and integrating it into CEBoard would mean writing a
similar code.

Best,
Alain



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.