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

Re: [TSVN] how should the UI look like

From: Toby Johnson <toby_at_etjohnson.us>
Date: 2005-04-08 21:34:05 CEST

J. Richard Mills wrote:

>1) Attempt the lock
>2) If it fails, throw up a box "Locked by So-and-so on mm/dd/yyyy hh:mm.
>Do you want to steal the lock?"
>3) Try to steal the lock, if *that* fails (i.e. due to permissions,
>server config, whatever), then throw the error back.
Instead of popping up a dialog for every failed lock attempt, perhaps if
any locks fail it could pop up one dialog, with a list of all items
which failed obtaining the lock. Each of these items would have a
checkbox, un-selected by default, along with the existing lock-token or
user or whatever the server returns.

The message could say "These items are already locked in another working
copy. You can attempt to 'steal' one or more locks from the existing
user if necessary, but you should do this only if the other user is
unavailable to release the lock themselves". Include Select All and
Select None buttons below the item list, and OK and Cancel buttons at
the bottom of the dialog. Unless the user checks any boxes, OK and
Cancel do the same thing; otherwise clicking OK attempts to steal the
locks. If stealing any locks fail, pop up a final dialog box indicating
this with OK as the only button.

The message could be tweaked some but I think it would be good to hint
that "stealing" locks is not a good thing to do.

>Also from the UI perspective: "lock" and "unlock" might not make
>intuitive sense to your general purpose dummy user (Audience #2 from
For better or worse, those are the terms agreed upon by the Subversion
devs, so I doubt TSVN would want to invent its own conventions.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Apr 8 21:34:28 2005

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.