Re: [Dgtnix-devel] dgtnix additions

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=windows-1252"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi, 
 
Alexander, I have written a minimal virtual board t in python. It is
usefull for testing the driver when we have no access to the real board. 
 
You can test it with 
./dgtnixVirtualBoard at the root of the dgtnix tree. 
 
Pierre 
 
 
 
 
 
Alexander Wagner a écrit :
<blockquote cite="mid...@tu..." type="cite">
 <pre wrap="">Pierre Boulenguez wrote:

Hi Pierre!

  </pre>
  <blockquote type="cite">
    <pre wrap="">I think that it would be cool if we could use the mailing list of dgtnix
to continue this discussion as it would allow people to see that things
are moving on around dgt under Linux.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Of course. That went private for some strange reason. (I
just had the wrong adressbook at hand... ;) Should have gone
through the list all the time of course.

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <pre wrap="">Ah, one point. I came accross this: it might be helpfull to have a
      </pre>
    </blockquote>
    <pre wrap="">dgtnix-function to rotate &gt;the board after initialisation. Ie. to set
the ClockRight-variable. It might be needed if one &gt;wants to implement
an "automatic rotation" functionality.

This has been implemented :)
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Cool. Just checked out the new version and I'll implement
this functionality in the driver engine. I hope I can
publish some beta soon. Unfortunately this weekend I've no
access to my board, and probably the next weekend will also
"feature" this problem. Still have this nasty issue with
eventhandling left but mainly as I had no time to repair it
yet. Otherwise I think it will be quite simple.

Anyway. I'm still thinking about two options for the driver
engine. Either to include it to dgtnix or to sourcefore it
itself. Did not come to a conclusion what would be the
better option. Including it in dgtnix obviously has the
advantage of an "all in one" package. sourceforging it for
its own on the other hand the advantage of visibility and
maybe easier access for the enduser. What's your opinion?

Till now I've written some documentation for it. Still have
to write the man page for the interface, but the users
documentation is done.

Maybe here on the list there is somebody who would like to
help with debugging? Currently necessary is a GUI that
features engine-engine tournament for either uci or xboard
compatible engines. xboard itself will do.

  </pre>
</blockquote>
</body>
</html>