3 [DONE] * Play from any position.
4 [PARTIALLY DONE] * Implement a real SDI interface.
6 * Configuration dialog.
8 This should not present problems, but is quite boring.
9 There are already pages for highlighting and clock configurations, but they should be linked in a tabbed configuration dialog similar to that of Kate, for example.
11 * General: language choice, automatically connect on startup, default variant, etc...
12 * Connection: manage ics connections and options.
13 * [DONE] Highlighting: manage highlighting patterns for the ics console.
14 * [DONE] Animations: animation speed, graphical effects, etc...
15 * [DONE] Theme: manage themes and theme options; choose default theme; associate themes with variants.
16 * [DONE] Movelist: colors, fonts, animations and graphical effects preferences.
17 * [PARTIALLY DONE] Clock: colors and fonts.
18 * [BROKEN] Engine: List of engines, with type, command line options, working path, etc...
22 Many things still have to be done to make the gui really user friendly (think about the Panda):
23 * Message boxes to notify the user of error, for instance while connecting.
24 * Restore a functional status bar.
25 [SKETCHED] * Add some game info between the pools (like "FICS, rated crazyhouse")
26 * Notify the user of Server/Engine events. I don't like the Babaschess-like popup when
27 i get a match request, i'd prefer an amarok-like notification.
31 [DONE] * Set up a decent installation system, maybe with a cool one-click windows (linux?) installer.
32 [MOSTLY DONE] * Improve default highlighting script.
33 [DONE] * Add support for multiple ICS interactions.
34 [MOSTLY DONE] * More robust ICS support: do not crash when testing invalid moves.
35 [DONE] * About dialog.
36 [DOME] * Choose an icon for the application.
40 * Better support for variants in pgn games
42 * Fix examination variant upgrade
43 * Game print support, through khtml?
44 * Ability to define a variant in some script language (ruby or lua or ...)
45 * Complete support for chess engines or variant specific AI.
46 * An advanced Edit Position mode, with the ability to edit a position for
47 an arbitrary variant, as well as the various flags such as the en passant
49 * Improve Examine Mode and Observe Mode:
50 Movelist support for examination is not as extensive as it could, and I don't know if it will ever be.
52 * [FIXED] Crash when going back to the starting position
53 * [FIXED] Moves are sometimes not correctly displayed even where there's enough information available.
54 Future possible features:
55 * Execute move immediately instead waiting the server response, when possible.
56 Note: this may prove hard to implement correctly, because one needs to filter out server responses
57 (after a suitable consistency check) so that they do not cause wrong updates if they come out when they
59 * Display variations correctly in the movelist, instead of always replacing mainline entries.
60 Note: hard to do, because the protocol sends very few information about the reason of a style12 update.