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