Backup locations

[jporkkahtc]

Backup location allows for a single global location, or next to the file being backed up.

Another option that would be useful is relative to the drive the file is located on.
This would allow me to keep backups and backup history with the files, but without cluttering the source file location.

Files edited on a flash drive would have their history stored on the flash drive.

Note that this would be for simple backups and for backup history.

[Dan]

So set the path to something like "..\backup\" and "c:\src\file1.cpp" goes to "c:\src\backup\file1.cpp.vsdelta"?

[jporkkahtc]

Yeah, though its unlikely I'd use ".."
Since a source tree is usually multiple levels deep just using ".." isn't good enough (and it doesn't work for files in the root of the drive).

Consider the backup files to be something like *.O files produced during a build.
Placing foo.o in the same folder as foo.c is the easiest thing to do, but also has a lot of problems.

Maybe this could be project or workspace specific, but that is probably too complex.

A simple "%" substitution would do it.
The user could set their backup path to "%D\vsdelta".
"%D" is replaced with the drive/partition of the source file.

The most complicated part here for Slick though would be handling backup history split among several locations.  Some of the locations come and go as the user adds and removes flash drives. Right now, its all in one place.




I don't use the non-history backup option, but as I was looking at these options today I was surprised how limited it is. I'd think that it would allow different backup naming conventions, and naming of the backup directory.  Especially on Linux, using a dot prefix to the name of the backup file or directory would be nice.