Re: reusable go board class in java?

[Dan Stromberg <strombrg@xxxxxxxxxxxxxxx>]

On Sat, 12 Dec 1998, Jeremy Thorpe wrote:

> 
> > 
> > My ideal java goban would be able to accept stones from the user and from
> > the computer, and would be able to display 9x9, 13x13 and 19x19.
> 
> does the goban know the rules of go (including (super-)ko)?  does it know

I actually need something that -doesn't- know the rules of go, including a
lack of knowledge of ko.  My intention is not to create a go AI, but a
"simplified go" AI, a learning tool for total newcomers to the game.

> how to take back a move, even if it means putting stones back on the

Being able to take back a move would be nice, but isn't critical for this
project.

> board?  can it take back as many moves as you want?  to me it sounds like
> this is what you need.  in openGo terminology, this is a board and referee
> class together (someone please correct me if this is wrong, but i think
> it's right)
> 
> or, on the other hand, do you simply want a goban that takes a set of
> nodes (361 vector), and displays them?  to me, there is not a lot of good
> ground between these two.  for example, if you want to implement a board
> that knows about ko, but can't undo, you cannot extend this class to be
> able to undo (because the ability to undo has to be built into the way
> some info is stored).