SteveKing wrote:
> Molle Bestefich wrote:
>> From the postings I've read so far, what most people would like to see
>> is if a file has the svn:needs-lock attribute, not the above.
>
> Definitely not: that property doesn't really tell you anything.
Yes it does :-).
It tells the user that "this file you need to take a lock on before
you start work on it".
It tells users that if they don't take a lock, they'll be screwing
over all their team mates.
> - If you don't have the lock, the file is readonly and you can't edit it.
Not true, editors are NOT guaranteed to care diddly-squat about
read-only being set.
Read-only is a residue from the good old DOS days, it's not guaranteed
to mean anything to a Windows application. Windows applications are
what TSVN has to do with.
> - if you have the lock, you can edit the file
And if you don't, you can as well. Whoop-ti-doo..
> in both cases the svn:needs-lock property is set.
So it is.
And it's effect should be that TSVN tells the user "you need to lock this file".
And an overlay would be the right way to do that, seeing as that's how
we tell the user everything else. Telling the user to switch all his
folders to 'Detailed' view and enable an extra column in Explorer to
show just this information is wrong.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Apr 13 20:44:04 2005