sylvinus / chessathome Goto Github PK

quand on change d'onglet sous chromium, le div ou whatever qui contient l'applet de jeu disparaît

Uncaught TypeError: Cannot read property 'options' of undefined

Show last move (easier than to look/scroll history, sometimes also history is cleared...). Usually this is implemented by highlighting (border) cell holding piece that did last move (on demand action)

Currently pawns automatically become queens upon promotion. A user needs to be able to select which piece to promote to (rook, bishop, knight or queen).

Also, I don't know if it currently does, but the AI also needs to consider minor promotions in its calculations.

the move order is inversed (first move is c7c5)
the black pieces should be downside.

I've installed Node program on my Ubuntu 11.04 box. The install went fine and the program works great for the first 30 minutes, then it just sits there. After a certain point, no matter how long I wait, it will not receive anymore work. If I Ctl^C and restart it starts receiving and processing work again. I have double-checked my network and the Ubuntu box and everything appears to be fine on this end.

To standard game notations. Also repopulate properly on page reload

Easier API ?

Black/White squares should be inverted.

So that the AI doesn't always play the same moves/openings

w/ "default"

Opening dictionary should be loaded & used

When blaying "as black" - board should be displayed accordingly - black pieces "closer" to player

1318946429614 'Fetched computing games : ' 1
1318946429682 'Fetching unresolved pos for game' 4e8dc6af85b793867c0003ad

/home/deploy/app/source/www/master/engines/distributed-mongo.js:179
models.Position.count({resolved:false,fen:{$in:_.keys(pos.children)}},
^
TypeError: Object.keys called on non-object
at Function.keys (native)
at Promise. (/home/deploy/app/source/www/master/engines/distributed-mongo.js:179:58)
at Promise. (/home/deploy/app/source/node_modules/mongoose/lib/promise.js:120:8)
at Promise. (events.js:64:17)
at Promise.emit (/home/deploy/app/source/node_modules/mongoose/lib/promise.js:59:38)
at Promise.complete (/home/deploy/app/source/node_modules/mongoose/lib/promise.js:70:20)
at /home/deploy/app/source/node_modules/mongoose/lib/query.js:856:15
at model. (/home/deploy/app/source/node_modules/mongoose/lib/document.js:163:5)
at model.init (/home/deploy/app/source/node_modules/mongoose/lib/model.js:161:36)
at /home/deploy/app/source/node_modules/mongoose/lib/query.js:854:12
^C

Chrome 11.0 - Characters on text "You are playing against 22 computers." ==> no space between "against" and "22". "22" written over previous characters

After checkmate (game won) - gets message "Checkmate! You lost!" (won -> lost)

"suicidal" moves (gave a lot of quality pieces) once seen problematic situation - resign would be more elegant...

Board not displayed from "black's point of view"

Possibility to have 3D display - better "visibility" when position is displayed in perspective

support endgame tablebase

there is at least one public tablebase web service at http://www.lokasoft.nl/tbapi.aspx
it does not have (most of) 6 men positions, but it's a good start

From William:

Are you sure the software is ready for prime time? I asked, because on the very third move of the computer's turn, it repeated its second move. In other words, its second move became its third move. Here is it: d2d4 g8f6 c2c4 d7d5 b1c3 d7d5.

See the attached screenshot of the starting game.

Can't reproduce but I can see how this could happen with the move display algorithm & some network oddness.

to stay up-to date and close to the iframe mode.

Two brower tabs "share" same game (also when opening new windows)

It would be good to ask user if castling was intended. Sometimes, by error, piece can "fall" to wrong cell and elegant castling is not possible any more. Maybe also when user starts it with tower (due to "incorrect" manual habit)