[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Copy (branch/tag) dialog: UI suggestion

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 26 Jun 2008 18:39:19 +0200

Auke Jilderda wrote:
> Hi,
>
> we (CollabNet) routinely deliver Subversion training and consulting.
> In these trainings, I consistently see many people be confused by the
> Copy (Branch/Tag) dialog. At present, it lists the source URL, the
> destination URL, and the source revision for the copy, mixing both WC
> and server based options in the source revision. Many people get
> confused about what is part of the source and what is part of the
> destination. In addition, many either don't realise or mix up that a
> copy can be from WC to WC, from WC to server, from server to server,
> or from server to WC.
>
> I suggest to (a) clearly distinguish the source and destination fields
> and (b) provide both URL and working copy as possible values for the
> source and destination. In other words:
> - from: URL (& revision) / location in a working copy
> - to : URL / location in a working copy
>
> Let me know what you think,

We designed the branch/tag dialog to be used exclusively for url
targets. For WC->WC copies, we have the right-drag feature which is
*much* better suited for that:
http://tortoisesvn.net/most-forgotten-feature

I think you should not tell your customers to use the branch/tag dialog
for WC->WC copies at all. Even though it *can* be used for that too, we
don't recommend it.

If you still think the dialog needs to be redesigned, can you maybe
provide some mockup to show us what you think it should look like?

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Received on 2008-06-26 20:13:31 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.