Either showing time stamps only for multiple version of the same file (same file path), or all files in general (meaning also files showing up only once in the archive).Hacker wrote:Which two concepts do you mean?
The first one will slightly slow down opening an archive with many files, but since ZPAQ needs a modern/powerful system anyway, I think I'll stick to it.
And I think I'll stick with a user configurable timestamp and not showing/allowing Windows forbidden chars, as we have enough Unicode chars (like this) to customize the timestamp and making the probability of generating duplicate filenames (name collisions) negligible.
Well, I wanted to make sure we both understand that such option would only work in connection with the 'Show all archive versions' option, otherwise it wouldn't make much sense.Hacker wrote:Well, without such an option, I really don't have any specific preference, can be as it is now?
So like we have it now, with the version sub-dirs ('Show all archive versions')? Or do you mean simply merging the version dirs, so that we'd have the same filename all over again in a dir?Hacker wrote:2. Never create filenames with timestamps appended
This means, listing in TC
Code: Select all
... c:\Backup.zpaq\ImportantDir\ImportantDocument.docx c:\Backup.zpaq\ImportantDir\ImportantDocument.docx c:\Backup.zpaq\ImportantDir\ImportantDocument.docx c:\Backup.zpaq\ImportantDir\ImportantDocument2.docx ...
I think I simply inform the user with a message box if such case is detected. In practice, such long names are not w/o troubles anyway, and the user could still re-customize the timestamp to make it a bit shorter. I might even make the timestamp position optional, likeHacker wrote:- problems if the filenames are really long and we reach the 255 char limit
Code: Select all
$n_≪$Y$M$D$h$m$s≫ $Y$M$D$h$m$s-$n $n,(%v) ...
How is that supposed to work? Like I said earlier, when merging all version dirs, TC can't request an individual file when the same file is listed multiple times with the very same path in the archive. And of course, when overwriting existing files, TC will ask the user itself for what to do, it's nothing I could intercept or bias with the plug-in.Hacker wrote:3. Only append timestamps to filenames in case multiple versions of the same file are extracted
If I simply merge the version dirs, they would show up anyway. I'd use the same rules as for any other file set.Hacker wrote:Concerning files that were deleted and are not present in newest versions of the backup I would not treat them any differently - consider the newest version as the current one.
But what do you mean exactly anyway? Having only "older" file versions the timestamp appended
Code: Select all
c:\Backup.zpaq\ImportantDir\ImportantDocument.docx (being the latest version) c:\Backup.zpaq\ImportantDir\ImportantDocument <2016-08-10 19:33:02>.docx c:\Backup.zpaq\ImportantDir\ImportantDocument <2016-07-16 15:21:31>.docx
That's exactly why I asked for how a sample archive structure would look like in TC with/without the option.
So all in all I will try to make it work as described: Merging the version dirs (i.e. removing them and moving all file paths to the base of the archive, like with the normal/non-version view)), all files with multiple version will have the customizable timestamp appended, warn user if some files are exceeding 255 chars due to the timestamp when opening the archive (no matter if for listing or extracting).