RE: Re: Feature / Bug - File lock icon, checking for modifications

> What about a policy "aquire a lock if you don't know if
> anybody is working on that file"?

It is absolutely possible for me to tell users to follow a rule. They
might even follow the rule most of the time. But computers are better
than users when it comes to automatically following a rule. Especially
if the rule would mean more mouse clicks for the user.

I think the user experience would be better, if they could already see
that someone had obtained a lock, with merely a glance down the list of
files, instead of having to perform some mouse clicks to find out.

If a user is going to work on a file, sometimes he/she wants to obtain a
lock, knowing he/she will probably work for a long time on this file.
But if he/she is only going to change one line, for example, create a
new flag variable within a class, they would rather just make the change
and commit. Nevermind get lock and release lock.

So although a policy of globally "needs lock" does in fact force users
to always check for lock before modifying a file, I'm sure some users
would prefer to have some of the checking work done for them, rather
than forcing them to do a little more work themselves.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Apr 26 00:39:58 2006