Recent changes to feature-requests

Create only one database

2007-10-25T21:19:58Z

As it is now, if you run md5files in a directory, the files database will be created in that directory. This is unfortunate if you want to find only new files in a given directory, rather than rescan the entire filesystem, as every single file would be found and md5'd.

My desire is to have the scripts know about the existence of the md5 database, perhaps through the single filesystem option, and modify md5files to act somewhat like remd5.sh in that it will remove _only_ files in the database matching the current path, and only if they're _not_ found in the file search that is performed.

single-filesystem option

2007-10-25T21:15:49Z

Implement a single-filesystem option. Always find the root directory of a file system and store the database there, unless instructed otherwise.

Create a GUI

2007-10-25T21:14:27Z

My thoughts for a GUI:

It can be just a frontend, but it should:
-list duplicate files
-color coding would be great (allow the user to select a palate of colors -- color blindness and such)
-on-the-fly modifiable directory priority (user moves a directory up; program searches through and makes all modifications to files affected by that directory as dupscript.pl would)
-output window with a tree and each directory/file that has duplicates, a list beside it showing where the duplicates are located for that directory (include subdirs/not). Possibly modify this as files are removed
-Color coding for the above matches-box for dupes marked for deletion/keep, and context menu/button (both, pls, and keyboard shortcut) to change such status
-Option to hide all dupes scheduled for deletion, hide all dupes _not_ scheduled for deletion, and show all dupes (not affecting the showing of where all a given file's dupes are located)
-Appropriate sorting
-Complete disallowal of deleting an entire group of duplicates, at least without 2-3 message boxes (one while selecting them all, ignore all for session and never show this dialog; one more when they actually go to delete the files)
-Project saving -- save this session, marked and unmarked dupes, all dupes found, and don't consider anything new when loading it (you can store this like dupscript.pl output -- comment masked files, uncommented files to be deleted.