Talk:PlayGo: Difference between revisions
No edit summary |
MtnViewMark (talk | contribs) No edit summary |
||
Line 13: | Line 13: | ||
Hello, who is working on this project? Why not use some of the [http://www.usgo.org/resources/computer.html software that's already out there]? |
Hello, who is working on this project? Why not use some of the [http://www.usgo.org/resources/computer.html software that's already out there]? |
||
[[User:Kibi|Kibi]] 18:29, 3 March 2008 (EST) |
[[User:Kibi|Kibi]] 18:29, 3 March 2008 (EST) |
||
---- |
|||
I'd be interested in helping out with this. I've done a collaborative goban in different environment. This project looks like it could use more detailed UI flow diagram. There probably isn't much sense in making use of existing software: Being a go board for play and replay isn't that difficult, and existing software doesn't interface with Sugar. Interfacing with KGS will be difficult, as the protocol is proprietary. [[User:MtnViewMark|MtnViewMark]] 01:30, 27 April 2008 (EDT) |
Revision as of 05:30, 27 April 2008
I'm very interested in seeing PlayGo work, but it's apparently stalled. (Hopefully those who were working on it are currently working on more important things.) As far as basic functionality is concerned, playing a 2-XO game is awkward (though not necessarily impossible).
The player who starts the game can play black or white stones (depending on which mouse button is clicked).
The second player (no idea what happens if more than 2 try to share) can only play black stones.
There's no enforcement of turns at all--either player can place a stone at any time.
When the second player joins the game, the first player's pieces remain on the board from their point of view, but do not appear on the second player's board.
I'm hoping I'll get clever enough to attack these problems, but I figured I would at least note them here.
Hello, who is working on this project? Why not use some of the software that's already out there? Kibi 18:29, 3 March 2008 (EST)
I'd be interested in helping out with this. I've done a collaborative goban in different environment. This project looks like it could use more detailed UI flow diagram. There probably isn't much sense in making use of existing software: Being a go board for play and replay isn't that difficult, and existing software doesn't interface with Sugar. Interfacing with KGS will be difficult, as the protocol is proprietary. MtnViewMark 01:30, 27 April 2008 (EDT)