Subject | Re: Paintshop and Corel |
From | Sandman |
Date | 11/26/2013 16:36 (11/26/2013 16:36) |
Message-ID | <slrnl99g1l.v9c.mr@irc.sandman.net> |
Client | |
Newsgroups | rec.photo.digital |
Follows | Tony Cooper |
Followups | Tony Cooper (1h & 16m) > Sandman |
What developer were you talking to when you said:Tony CooperTony CooperSandman
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.
Just like automatic backup, then. Heeey, sounds like what I've been saying all along, doesn't it?
Think really hard and you might begin to understand that an automatic backup action follows the protocol set by the developer.
So clicking a button is now "adding his own protocol"? Even in the cases where you can determine frequency, you would call clicking a popup and choosing "hourly" (for instance) that the user is "adding his own protocol"?Tony CooperThe backup protocol is different because it can involve user-defined additions to the built-in protocol.Sandman
"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?
And the user adds his own protocol requirements of frequency and destination to the backup protocol of the developer.
Backup is not "a protocol" as I have pointed out in another post. Backup is an action that will run based on the protocol used by the developer and the user (if user-defined steps can be added). The "backup protocol" describes the protocol employed to determine what is done, but just "backup" describes the action.Tangle tangle tangle :)
I'm not talking about file copying at all. I prefer to keep the discussion centered on the backup protocol.Yeah, analogies that expose weaknesses in your reasoning have no place here! :)
Ok - but in the image above, the user does determine the target destination of the backup - which is one of the things you said above was "adding their own protocol", right?Sandman
Here is the user implementing backup in an automatic system:http://tinyurl.com/pju45q7Please define in clear terms how he or she is adding items to the protocol.Tony Cooper
The user is not adding anything to the protocol by clicking any of the boxes. That's a step in backup action routine.
It's the same example.The user determines a backup protocol that determines the frequency of backups and the location of where the backups are sent.Sandman
Again, he or she attaches an external drive, and this is shown:http://tinyurl.com/pju45q7Tony Cooper
You have used the same link for both examples.
Clicking that button is the *ONLY* action the user has done in terms of backup. Like I've said many times. He or she connects an external drive (or OSX senses a Time Capsule on the network) and it automatically asks the user this question. When clicking "use", the user interaction with the backup process has ended. The frequency and target destination is set and done.SandmanTony Cooper
No settings for frequency, and by hitting that button, the system already knows the location. Boom, all done. Automatic backup every hour around the clock.
I am not an Apple user, so I don't know what is done in the way of user-defined additions to the backup protocol, but I assume the user has set the location at some point. That's a user-defined addition.
Tangle tangle tangle :)Tony CooperSome programs, but not all by any means, allow the user to add this information and have that protocol followed automatically in the future.Sandman
So some backup functions are protocols and some are not? How automatic does it need to become to not be a protocol?
No backup functions are protocols. Try to get this into your head. A function is not a protocol. A protocol can call for a function, though.
If you are going to continue this, do some research on what "protocol" means in this context.Of the two of us, I'm the only one that seems to know.