code.delx.au - gnu-emacs-elpa/blob - TODO

   1 - Feature work remaining:
   2
   3   2.0
   4     annotations
   5     chatting
   6     clocks
   7   2.x
   8     display/database tie-in
   9     analysis/highlight tools
  10     bughouse/crazyhouse
  11
  12 - undoing a single move (my move) and moving again, causes
  13   chess-algebraic to get a little screwed up
  14
  15 - the game should go inactive once I lose by stalemate/checkmate
  16
  17 - detect draw/resign/abort/retract, etc., from ICS and common engines
  18
  19 - in chess-engine-filter and chess-ics-filter, if an error is
  20   encountered, skip that line so the same error isn't triggered again
  21
  22 - SPACE to pass, then try to move (against an engine) fails saying
  23   it's not our turn to move
  24
  25 - Add support for adjournments; also, implement this is such a way
  26   that an e-mail or postal game is basically a game that's adjourned
  27   after every move
  28
  29 - There needs to be much more robustness; it's too easy to get the
  30   game into an unplayable state right now
  31
  32 - Break my dependency on cl
  33
  34 - Use more asserts throughout the code
  35
  36 - Read-only mode needs to be more vigorous.  There's nothing
  37   preventing the user from using M-x commands.
  38
  39 - Complete chess-pgn-mode's automatic entry
  40
  41 - Make any game-modifying commands in a display use C-c C-?
  42
  43 - Use MIME attachments (application/x-chess-pgn) for sending e-mail
  44   chess games back and forth.
  45
  46 - Copy some of ics.el's nicer functionality into chess-ics.el
  47
  48 - Add support for ICS observing
  49
  50 - Make the mode-line much more informative, with information on who is
  51   playing, etc.
  52
  53 - Use server-side sockets in chess-network, if Emacs supports it
  54
  55 - Support auto-saving of games to PGN, and saving them at appropriate
  56   points; this will require database interaction support
  57
  58 - Allow ASCII displays to use a separate frame
  59
  60 - In edit mode, mouse-2 and mouse-3 should provide a drop-down list of
  61   pieces the square can be set to.  Cursor movement is really not the
  62   best for chess-images.  I still need to figure out how best to
  63   handle cursor-type with that display.
  64
  65 - Still need to test many areas: position editing
  66
  67 - Implement engine options; then, in chess-puzzle set the option that
  68   tells the engine not to resign.
  69
  70 - Remote displays are horribly insecure.
  71
  72 - Resize the chess board on a window resize event, if possible.
  73
  74 - Add chess-game-strip-annotations, for removing all annotations from
  75   a game object
  76
  77 - Let the user specify a default size for the chess-images display
  78
  79 - Port image display code to XEmacs
  80
  81                           Training features
  82
  83 - Allow the opponent to give hints.
  84
  85 - Add a warning mode that will use the results of an analysis to warn
  86   the user (and ask for confirmation) before doing something that
  87   might lead to an inferior position.
  88
  89 - Add a chess tutor program, to teach people how to play chess
  90
  91                           Analysis features
  92
  93 - Add an engine function for obtaining an evaluation of the current
  94   position.  Then, allow M-x chess to startup a non-game oriented
  95   engine, solely for the purpose of submitting position evaluations,
  96   and displaying the result in the modeline.  (Also, look at crafty's
  97   kibitzing feature).
  98
  99 - Add a Map command, that will colorize the squares depending on
 100   whether they are reachable by either side.  Green if reachable by
 101   you, Red if by your opponent, and blue if by both.  With a prefix
 102   argument, colorize only the squares that have pieces on them.  This
 103   is a stable modes that remains in effect until turned off.  It also
 104   requires the ability to pass a color to the chessboard highlighting
 105   routine.
 106
 107 - Using gnuplot-mode, allow evaluation trends to be plotted
 108
 109 - Add an analyze command that will indicate which pieces are defended,
 110   how well, which are attacked, which moves would increase
 111   defense/attack/both, etc.  Basically, everything that can be known
 112   about the current board, and one move ahead (on both sides).
 113
 114                          BEFORE FINAL RELEASE
 115
 116   profile
 117   mem profile
 118   docstring
 119   texi
 120   elint
 121   checkdoc