1
Important for Thunar 1.0
2
========================
4
- Add ThunarVfsFlags, which specifies various flags for the job starters
5
(like thunar_vfs_copy_files, etc.). One important flag would be
6
THUNAR_VFS_FLAG_ERROR_ON_OVERWRITE, which tells the job not to ask the
7
user when the target exists, but to fail directly (the flags could also
8
be part of thunar-vfs-interactive-job.h, as they're only interesting
11
- We need a way to "refresh" folders after a "Cut"-operation with Nautilus.
12
With local folders - with not many files inside - the move is too fast!
14
- The ThunarTrashFile constructor needs some rework, as it's currently
15
mostly brain-dead. Should probably be splitted into several functions.
16
In addition the ThunarTrashFile should enable the monitoring on the
17
real file in order to stay informed about changes.
19
- The ThunarTrashFolder class should watch the trash manager and the
20
trash cans for changes.
22
- Use better way to handle system flavours than simply (mis)using
23
AC_CONFIG_LINKS(), which is pretty messy for this purpose.
25
- Check getmntinfo() or getfsstat() for ThunarVfsVolumeManagerBSD, which
26
might be faster than several statfs() calls.
28
- The layouting code for ThunarLocationButtons is still buggy. Problem shows
29
with paths that include a very long directory; you cannot scroll to the
30
last path component then.
32
- A design for the ThunarTreePane framework must be developed and later
35
- The preferences must be sorted out and a suggestion for both a good
36
set of preferences and a layout for the preferences dialog must be
37
developed and presented.
39
- A design for the ThunarDesktopView module must be developed and later
42
- We need a suite of unit tests and probably high-level tests, that enable
43
us to test parts of the file manager automatically and isolate bugs
46
- Setup gtk-doc to present developers with the internal API of Thunar
47
to ease development of core modules (and later plugins).
49
- Write good user documentation. Must be both precise and complete.
51
- Design (UI design this time) the file properties dialog, develop
52
a software design and implement it.
54
- We need some easy way to manage diagrams and related developer
55
information, which also includes results from discussions on
58
- The HACKING file must be updated with strict rules about how
59
development of Thunar core modules is to be done, and what
60
material each developer in addition to the source code.
added
removed
TODO
