]> code.delx.au - gnu-emacs-elpa/blob - TODO
*** no comment ***
[gnu-emacs-elpa] / TODO
1 - Feature work remaining:
2
3 2.0
4 clocks
5 annotations
6 chatting
7 2.x
8 display/database tie-in
9 analysis/highlight tools
10 bughouse/crazyhouse
11
12 - Make the drawing/highlighting code just touch single squares, rather
13 than redrawing the whole board each time (fast though this is,
14 touching single squares is all that's necessary, and it would be
15 even faster)
16
17 - Fix highlighting in chess-plain when chess-plain-spacing is set.
18 chess-coord needs to be applied to a larger area, and also the way
19 highlight locations are found needs to be recalculated.
20
21 - The highlighting code is broken for a different reason. I'm
22 thinking about changing all of the highlighting functions to USE
23 properties in order to find out where the highlighting region should
24 begin.
25
26 - Move keyboard shortcutting and mouse selection into their own
27 modules
28
29 - the game should go inactive once I lose by stalemate/checkmate
30
31 - when a clock runs down, indicate this in the modeline, and all the
32 user to call-flag in order to win on time
33
34 - parse out the time strings from ICS
35
36 - detect draw/resign/abort/retract, etc., from ICS and common engines
37
38 - in chess-engine-filter and chess-ics-filter, if an error is
39 encountered, skip that line so the same error isn't triggered again
40
41 - SPACE to pass, then try to move (against an engine) fails saying
42 it's not our turn to move
43
44 - Add support for adjournments; also, implement this is such a way
45 that an e-mail or postal game is basically a game that's adjourned
46 after every move; use BBDB if available
47
48 - Allow databases to return a game moniker, which can be used to
49 reference that game again
50
51 - There needs to be much more robustness; it's too easy to get the
52 game into an unplayable state right now
53
54 - Break my dependency on cl
55
56 - Use more asserts throughout the code
57
58 - Read-only mode needs to be more vigorous. There's nothing
59 preventing the user from using M-x commands.
60
61 - Complete chess-pgn-mode's automatic entry
62
63 - Make any game-modifying commands in a display use C-c C-?
64
65 - Use MIME attachments (application/x-chess-pgn) for sending e-mail
66 chess games back and forth.
67
68 - Copy some of ics.el's nicer functionality into chess-ics.el
69
70 - Complete the ICS12 parser, based on Mario's comments
71
72 - Add support for ICS observing
73
74 - Make the mode-line much more informative, with information on who is
75 playing, etc.
76
77 - Use server-side sockets in chess-network, if Emacs supports it
78
79 - Allow ASCII displays to use a separate frame
80
81 - In edit mode, mouse-2 and mouse-3 should provide a drop-down list of
82 pieces the square can be set to. Cursor movement is really not the
83 best for chess-images. I still need to figure out how best to
84 handle cursor-type with that display.
85
86 - Still need to test many areas: position editing
87
88 - Implement engine options; then, in chess-puzzle set the option that
89 tells the engine not to resign.
90
91 - Remote displays are horribly insecure.
92
93 - Resize the chess board on a window resize event, if possible.
94
95 - Add chess-game-strip-annotations, for removing all annotations from
96 a game object
97
98 - Let the user specify a default size for the chess-images display
99
100 - Port image display code to XEmacs
101
102 Training features
103
104 - Allow the opponent to give hints.
105
106 - Add a warning mode that will use the results of an analysis to warn
107 the user (and ask for confirmation) before doing something that
108 might lead to an inferior position.
109
110 - Add a chess tutor program, to teach people how to play chess
111
112 Analysis features
113
114 - Add an engine function for obtaining an evaluation of the current
115 position. Then, allow M-x chess to startup a non-game oriented
116 engine, solely for the purpose of submitting position evaluations,
117 and displaying the result in the modeline. (Also, look at crafty's
118 kibitzing feature).
119
120 - Add a Map command, that will colorize the squares depending on
121 whether they are reachable by either side. Green if reachable by
122 you, Red if by your opponent, and blue if by both. With a prefix
123 argument, colorize only the squares that have pieces on them. This
124 is a stable modes that remains in effect until turned off. It also
125 requires the ability to pass a color to the chessboard highlighting
126 routine.
127
128 - Using gnuplot-mode, allow evaluation trends to be plotted
129
130 - Add an analyze command that will indicate which pieces are defended,
131 how well, which are attacked, which moves would increase
132 defense/attack/both, etc. Basically, everything that can be known
133 about the current board, and one move ahead (on both sides).
134
135 BEFORE FINAL RELEASE
136
137 profile
138 mem profile
139 docstring
140 texi
141 elint
142 checkdoc