"To-do" list for Arasan 4.0, June 1997

This is a list of known problems or shortcomings of the program, and
suggestions for things to add or improve.  They aren't in any order
of priority or importance.

1. The piece bitmaps are ugly and don't scale well when the window
is shrunk.  It is not clear how to fix this.  We could use a fixed
number of board sizes (like Winboard), use vectors or metafiles to draw
the pieces, or come up with a smarter scaling algorithm for bitmaps.
Another suggestion is to use a True Type font for the pieces.

2. There is no provision for setting up a board position interactively.

3. It would be nice to have a user interface to allow adding opening
moves (currently this requires rebuilding the book file with a console
program). 

4. The "makebook" program keeps the book in memory while processing,
which is not a good idea if you need to build a very large opening book.
It should store more intermediate data on disk.

5. Context-sensitive help is not yet supported.

6. It would be nice to be able to load and browse a .EPD file, as can
be done for .PGN files.

7. Arasan cannot print the chess board.  Note: there is some printing
support in the code, but it is not fully functional.  The display code
needs to change for printing, since printers cannot do the raster
operations used in Display::draw_piece.

8. The PGN parser ignores comments in PGN files - it would be nice to
display them somehow as the game is replayed.

9. The testsrc program should probably be converted to consume .EPD files.

10. The scoring module should be extended to allow use of endgame
databases.

11. Arasan should handle the 50-move drawing rule.

12. Arasan should make and accept draw offers, when appropriate.

13. Font handling should be cleaned up.  Right now most fonts
are set to Arial, rather than following the user's preference
as set in the Display properties part of Control Panel.

14. Arasan should have an option to set the PGN header contents,
as Winboard does.

15. Arasan doesn't handle all the syntax that is part of the
PGN standard.  For example, PGN files that include a FEN
tag (to specify the starting position) are not supported.
