Re: weakness in locking UI

Ben Collins-Sussman wrote:

> For now, I think I'm going to build the getlocks_test binary on OS X
> and just give it to this team to use as a workaround. But I'd love to
> hear ideas about how to make the commandline client itself more
> usable. (For GUI tools like TSVN, I imagine some sort of "locks
> report" would be a nice thing to add.)

In TSVN, you can use the "check for modifications" dialog, then sort by
the 'locks' column to get all locks and owners in the whole working
copy. Not sure if a separate 'locks report' would help that much.

What many users often request on the TSVN list is an overlay for locked
files, as well as a separate column for who locked the file. But that
could only be done if that information is cached in the working copy
itself (I can't keep a connection open to the repository from the
explorer, that would make the whole system so slow it would be unusable).
The problem I see with that approach is that this information would only
be updated on e.g. commits/updates/st -u/...

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org