Subject | Re: Paintshop and Corel |
From | Sandman |
Date | 11/26/2013 09:32 (11/26/2013 09:32) |
Message-ID | <slrnl98n6e.uhi.mr@irc.sandman.net> |
Client | |
Newsgroups | rec.photo.digital |
Follows | Tony Cooper |
Followups | Tony Cooper (6h & 46m) > Sandman |
I... don't know how to write it in any simpler form.SandmanTony Cooper
It is automatic *for the user* and not a protocol *for the user*,
I have no idea what you're trying to say there. What does "for the user" mean?
Just like automatic backup, then. Heeey, sounds like what I've been saying all along, doesn't it?SandmanTony Cooper
just like erasing a hard drive isn't a protocol *for the user* since all they do is press a button,
In this case, though you are describing it poorly, you are referring to an action that does not need a user-defined protocol because the user does not need a standard set of steps to accomplish the action.
The backup protocol is different because it can involve user-defined additions to the built-in protocol."Can"? Are you now saying that both file copying and backup are governed by protocols but you would only call backup a "protocol" since you "can" add things to this supposed protocol?
The user determines a backup protocol that determines the frequency of backups and the location of where the backups are sent.Again, he or she attaches an external drive, and this is shown:
Some programs, but not all by any means, allow the user to add this information and have that protocol followed automatically in the future.So some backup functions are protocols and some are not? How automatic does it need to become to not be a protocol?