2010/12/29 Petr Baudis <[email protected]>:
> Hi!
>
> On Tue, Dec 28, 2010 at 01:30:48PM -0200, davi vidal wrote:
>> Sorry. I forgot to add that I'm storing the moves in SGF format.
>> What I'm going to do: get a Go position (dunno how, that's why I'm
>> asking about FEN), encode in JSON, parse in JavaScript and draw in
>> HTML. As backend, I'm using Ruby, so I can have something as
>> 8b10/19/19... and parse using regex.
>>
>> As far as I can understand from your posts and the previous
>> thread, the only drawback is the *ko rules/repetition that I *will*
>> miss with FEN, right?
>
> My approach would be either:
>
> (i) Just do away with server backend and do all the go rules and SGF
> parsing in JavaScript. If Eidogo can do it, you can too. :-) (Or why not
> just use Eidogo altogether?)
>
Just because I can turn off my JS or try to access through my cell
phone. Otherwise, I'll use JS as much as I can. :-)
As for not using Eidogo: I don't like Eidogo's license. I prefer MIT or BSD.
> (ii) Use FEN plus list of disallowed moves. The backend can determine
> the disallowed moves from the ko rules and whatever, but if your
> frontend is just "dumb display", you do not care about the state or ko.
> You just care about which moves are disallowed, so pass that list of
> coordinates along. Or even better, encode them in the FEN with a special
> character!
>
I didn't understood your suggestion. Could you clarify?
Did you mean somethng like this?
19/bbb[...] b - a10/b15/j9 0 0
[position] [side to move] [ko point] [disallowed moves] [white
prisoners] [black prisoners]
For simplicity's sake, I'm starting to consider only the Japanese
rules, for now. I'll bother about the other after. :-)
davi
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
