PDA

View Full Version : Permanent "Backup Settings" menu instead of "Open Recent" menu


porg
07-11-2007, 08:09 PM
"File > Open Recent" has some disadvantages

I.e.: the order is always changed, number of items might be limited(?),...

I would suggest this: A permanent menu "File > Settings" which displays all files ending in .dset from "~/Library/Application Support/SuperDuper!/Saved Settings" in a user determined order. Preferences: Sort settings ascending/descending/individually (individually lets the user sort a list by dragging and dropping list items), Softlinks to .dset files are followed Y/N

Here is my personal naming convention, which works pretty fine for a lexical order. I share this convention here as it might help some other users.

<Sourcename [Targetname]> - <Parts which are Saved> - <During Copy Method>

Examples:

sno - all - erasethencopy
sno - all - smartupdate
sno - users - erasethencopy
sno - users - smartupdate
snd - all - smartupdate
snd - audio - smartupdate
snd snd-backup-longterm - all movies - smartupdate
snd snd-backup-daily - currently editing videos - smartupdate
snd - text and development - smartupdate

Note:

<placeholder>
[optional argument]
My Volume names are in this format: xxt[-bk-[subname]]
xx are my initials
t is the type of disk
Examples: o "Operating System and User Folders", d "Data", s "Share"
Mostly I only gave the sourcename, because I only use one backup generation. If you use multiple backup generations you should write sourcename targetname, i.e "volume to volume-bk-daily"

Terminology Suggestion:

Instead of these non-descriptive menu names: Save, Save As
I would suggest more descriptive menu names for future releases, such as: Save Backup Setting, Save Backup Setting As

dnanian
07-11-2007, 08:13 PM
Thanks for your suggestions!

UniAce
07-14-2007, 12:45 PM
I agree with porg that the interface could use improvements in how saved settings and/or scripts are handled. (In fact, I keep forgetting what the difference is between scripts and settings. I know I'm sure it's in the documentation, but if the design was improved enough then referring to the manual wouldn't be necessary; the answer would just be obvious.)