1 - Feature work remaining:
6 analysis/highlight tools
8 display/database tie-in
10 - undoing a single move (my move) and moving again, causes
11 chess-algebraic to get a little screwed up
13 - the game should go inactive once I lose by stalemate/checkmate
15 - detect draw/resign/abort/retract, etc., from ICS and common engines
17 - in chess-engine-filter and chess-ics-filter, if an error is
18 encountered, skip that line so the same error isn't triggered again
20 - SPACE to pass, then try to move (against an engine) fails saying
21 it's not our turn to move
23 - Add support for adjournments; also, implement this is such a way
24 that an e-mail or postal game is basically a game that's adjourned
27 - There needs to be much more robustness; it's too easy to get the
28 game into an unplayable state right now
30 - Break my dependency on cl
32 - Use more asserts throughout the code
34 - Read-only mode needs to be more vigorous. There's nothing
35 preventing the user from using M-x commands.
37 - Complete chess-pgn-mode's automatic entry
39 - Make any game-modifying commands in a display use C-c C-?
41 - Use MIME attachments (application/x-chess-pgn) for sending e-mail
42 chess games back and forth.
44 - Copy some of ics.el's nicer functionality into chess-ics.el
46 - Add support for ICS observing
48 - Make the mode-line much more informative, with information on who is
51 - Turn on memory gc collection messages, and see how much of a pig
54 - Make as much of chess-game/ply/pos, etc., defsubst as possible.
56 - Create a series of generic functions and predicates, so that users
57 can say (chess-position OBJECT) or (chess-move OBJECT), without
58 needing to know the type of OBJECT.
60 - Change chess-display-set-... to chess-display-set, and make it use
61 the new generic functions.
63 - Use server-side sockets in chess-network, if Emacs supports it
65 - Support auto-saving of games to PGN, and saving them at appropriate
66 points; this will require database interaction support
68 - Allow ASCII displays to use a separate frame
70 - In edit mode, mouse-2 and mouse-3 should provide a drop-down list of
71 pieces the square can be set to. Cursor movement is really not the
72 best for chess-images. I still need to figure out how best to
73 handle cursor-type with that display.
75 - Still need to test many areas: position editing
77 - Implement engine options; then, in chess-puzzle set the option that
78 tells the engine not to resign.
80 - Remote displays are horribly insecure.
82 - Resize the chess board on a window resize event, if possible.
84 - Add chess-game-strip-annotations, for removing all annotations from
87 - Let the user specify a default size for the chess-images display
89 - Port image display code to XEmacs
93 - Allow the opponent to give hints.
95 - Add a warning mode that will use the results of an analysis to warn
96 the user (and ask for confirmation) before doing something that
97 might lead to an inferior position.
99 - Add a chess tutor program, to teach people how to play chess
103 - Add an engine function for obtaining an evaluation of the current
104 position. Then, allow M-x chess to startup a non-game oriented
105 engine, solely for the purpose of submitting position evaluations,
106 and displaying the result in the modeline. (Also, look at crafty's
109 - Add a Map command, that will colorize the squares depending on
110 whether they are reachable by either side. Green if reachable by
111 you, Red if by your opponent, and blue if by both. With a prefix
112 argument, colorize only the squares that have pieces on them. This
113 is a stable modes that remains in effect until turned off. It also
114 requires the ability to pass a color to the chessboard highlighting
117 - Using gnuplot-mode, allow evaluation trends to be plotted
119 - Add an analyze command that will indicate which pieces are defended,
120 how well, which are attacked, which moves would increase
121 defense/attack/both, etc. Basically, everything that can be known
122 about the current board, and one move ahead (on both sides).