Important for Thunar 1.0
========================

 - When copy&paste in the same folder, adopt Nautilus' behaviour of
   automatically creating a copy of the original file, guessing names
   automatically.

 - We need a way to "refresh" folders after a "Cut"-operation with Nautilus.
   With local folders - with not many files inside - the move is too fast!

 - The ThunarTrashFile constructor needs some rework, as it's currently
   mostly brain-dead. Should probably be splitted into several functions.
   In addition the ThunarTrashFile should enable the monitoring on the
   real file in order to stay informed about changes.

 - The ThunarTrashFolder class should watch the trash manager and the
   trash cans for changes.

 - Use better way to handle system flavours than simply (mis)using
   AC_CONFIG_LINKS(), which is pretty messy for this purpose.

 - Check getmntinfo() or getfsstat() for ThunarVfsVolumeManagerBSD, which
   might be faster than several statfs() calls.

 - The layouting code for ThunarLocationButtons is still buggy. Problem shows
   with paths that include a very long directory; you cannot scroll to the
   last path component then.

 - A design for the ThunarTreePane framework must be developed and later
   be implemented.

 - The preferences must be sorted out and a suggestion for both a good
   set of preferences and a layout for the preferences dialog must be
   developed and presented.

 - A design for the ThunarDesktopView module must be developed and later
   be implemented.

 - We need a suite of unit tests and probably high-level tests, that enable
   us to test parts of the file manager automatically and isolate bugs
   early.

 - Setup gtk-doc to present developers with the internal API of Thunar
   to ease development of core modules (and later plugins).

 - Write good user documentation. Must be both precise and complete.

 - Design (UI design this time) the file properties dialog, develop
   a software design and implement it.

 - We need some easy way to manage diagrams and related developer
   information, which also includes results from discussions on
   thunar-dev.

 - The HACKING file must be updated with strict rules about how
   development of Thunar core modules is to be done, and what
   material each developer in addition to the source code.

