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

* better version detection for RSS
* markdown-alike functionality for diff view
* proper support for different text encodings (Qt already has everything,
  we just need to present that to the user and store the view settings in
  a custom attribute)
* 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.
* double-click -> diff view of items in the commit dialog
* TortoiseSVN-alike completion of file/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
* add functionality which is currently missing from monotone (update, ...)
* 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
* implement some properties dialog to show more info on the currently opened
  workspace / database (needs db info command in automate)
* implement drag'n'drop and proper rename support (stubs)
* make coloring throughout the application configurable, find saner defaults
  for the currently redish/greenish diff output
* 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...
* think about a dynamic sidebar which provides context actions if an item in
  the workspace view is marked -> better than the hidden right-click menu
  and fancier than a toolbar which enables / disables certain elements

