Hi,

There are some issues that are not so well defined in GTP v2.
Maybe GTP v3 should be released to avoid too much legacy later?

1.
The most important thing is controller - engine architecture.
There are situations that engine would like to have the control. For instance
When he want to send commands to GUI to draw something while he is working.

In gogui this is solved by using stderr to send those commands, but:
- stderr is not network transparent
- syntax is not standardized
- there is no confirmation about success / failure for those commands.

2.
The second thing is that there are many variables in the engine (komi,
board size, time, etc).
Developers tend to have more of them to control various parameters of
the engine.
End users could like to have some control over strength of the algorithm, etc.

3. If GTP would supports chats, KGS would probably implement it.

4. Opponent identification.

5. Interrupt. Users do not always want to wait until the program finish work.
 GoGui uses comment "#interrupt" to do it, but this is a hack.
(this is somewhat related to 1.)

6. Position setup. I had conversation with Marcus about setup in GoGui.
And we concluded that there should be a separate command for that.

Would You like to have those issues solved?
I hope we can get somewhere. :)

Best Regards,
Łukasz
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/

Reply via email to