[computer-go] Collaboration project. Once again

[Markus Enzenberger]

I know. This is why I tried to explain, that I usually debug the engine 
directly without GoGui. The disadvantage would be, if the engine wants to 
draw something on the GUI during the debug process, which is not possible.
It's no problem for me, because our engines don't output graphical stuff 
during a move generation.

But there is no doubt that the seperation and decoupling of tools and engines 
can have disadvantages too. In the end you have to pay a price and compare 
the overall advantages and disadvantages.

- Markus

On Saturday 05 August 2006 13:11, Magnus Persson wrote:
> I have the same problem. My next version of Viking will not have a nice
> userinterface so I plan to use GoGui. It is great for moving around in an
> sgf file and try things but the problem is when you want to run the program
> in the debugger. I cannot start GoGui from Delphi and then let it attach
> Viking.
>
> I am able to do this with KgsGtp using pipes. My engine executes first and
> starts KGSgtp using pipes. Perhaps there is some obvious way to do this
> with Gogui as well, perhaps using TCP/IP. There are some tools but I have
> not looked
> into that yet.
>
> -MP