Stefan Küng schrieb:
> Can you make a suggestion on how we should word this in a better way so
> users can understand it?
1. We (developers/doc writers) should consider a re-structuring of the
repository contents as a normal operation. So it should be supported and
well-documented. Not everyone gets the structure done in the first run
and, hey, the support for re-structuring is what makes SVN unique. :) So
I suggest a separate chapter/section labeled something like "Directory
re-structuring: The easy way" - text tbd.
2. Side note: If I were a beginner, I would consider "Relocate" to be
the proper operation because "Switch" is not specific enough. "Relocate"
is a very concrete word suggesting the expected operation but not
required very frequently. "Switch" is a very general term that would not
jump into my mind after re-structuring.
2. I think the warning dialog should contain a "Help" button like the
original relocate dialog - the user does not expect such a warning, he
should be offered further information from here, not by aborting and
re-running Relocate to find a Help button. A button directly to the
"Switch" command from the warning dialog would be cool, something like a
second chance to use the correct operation.
3. The warning dialog and the Relocate dialog might be swapped in order,
so the warning is presented before the harmless-looking Relocate dialog.
4. Maybe SVN could change in a way that any applied 'Relocate' command
would automatically determine the correctness of the operation? Is this
possible at all? Couldn't the 'new' repository be contacted and verified
against the WC before updating the WC?
The message box I would expect would be something like the following,
with better English of course:
= TortoiseSVN - Relocate Warning
*ATTENTION:* The Relocate command is only used if the URL of the
repository root has changed due to a server IP address change, protocol
change (f.e., http:// to https://) or a change of the repository root
path in the server setup.\n
*This is a very infrequently used operation* and applies neither if you
want to move to another Subversion repository nor if you want to switch
to another branch or directory *within the same repository*.\n
To move to another Subversion repository, perform a clean checkout from
the new repository location.\n
To associate your working copy with another branch or another directory
within the same repository, use the Switch command below or from the
An inadequately used Relocate command *will corrupt your working copy!*
If you are unsure whether Relocate is the correct operation, it probably
is not and you should consult *Help* below.
[Relocate] [Switch] [Cancel] [Help]
What do you think?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Oct 11 19:49:12 2005