This file lists some ideas what could be improved / implemented in guitone
mid- to longterm in no particular order, for a list of definite changes see
the TODO file:

* code rendering for graph view in the changeset dialog (and think about
  a nice way to include this view in the per-file history as well)
* AppleScript interface for the driver mode
* better version detection for RSS
* markdown-alike functionality for diff view
* make the FileDiff and RevisionDiff dialogs more error-aware if they're
  given two revisions which have nothing in common or if the diff is
  restricted to a path which is invalid in either revision, or if we're
  trying to get_file a file which does not exist in either one...
  stuff like that.
* TortoiseSVN-alike completion of function names in the commit dialog
* make changed items view configurable (currently they're just bold)
* integrate support to make guitone a kpart module under KDE
* use QDialogButtonBox to place the ok/abort buttons in the correct order
  based on the platform)
* add unit tests for all the internals
* make file-saving rollback'able if aborted / on error
* make more use of typedefs to define more clearly what kind of parameters
  a certain method accepts. If everything is just labeled as QString this
  won't help the code readability a lot...
* implement a db statistics panel which basically returns the data mtn db info
  has (need an automate version of this)
* implement a thread info panel which shows the currently running threads/mtn
  instances, shows their workload and the items in the queue and allows to
  abort / restart single threads
* test and optionally download / install a known working version of monotone
  inside the windows installer
