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

Re: [TSVN] What overlays do we NEED

From: Nicklas Norling <exinor_at_exinor.net>
Date: 2005-04-14 14:38:58 CEST

SteveKing wrote:

>2005/4/14, Simon Large <slarge@slarge.plus.com>:
>>Peter McNab wrote:
>>>Are we going to see the locked status for files burried deep in a
>>>directory structure propogated to the top like the modified status?
>>It looks as if we are tending towards displaying 'read-only' rather than
>>'locked-by-me', and that one should not propagate back up.
>Also: both 'read-only' and 'locked-by-me' are not real Subversion
>status but different states of a file.
Having had the opportunity to work with one of the Microsoft Outlook UI
designers, I've
learned that it's often a good idea to decide upon a metaphor. As an
example use the dialog
metaphor for displaying messages to a user.
I've tried to analys how I use and perceive the overlays when I use TSVN
and I've come to
the conclusion that basically the overlays are a visual diff between
what's in the repo (when
I last updated) and in my WC. I can see when I've added a file to my
project but not to
svn, I can see when files have been added to svn but not yet committed
to the repo. I can
see deleted folders (but not files) etc. Is this how others see it also?
If so, could it be used
for figuring out how (or even if) to do locking overlays or remove/add
other overlays?
Based on my experience it's possible it could provide at least a good
guide. And if nothing
else it could provide consistency in the UI towards the end user.

Suppose we assume that we want to visually diff between the repo and the
WC by using
overlay icons, what would that hint me about locking overlay? Can a lock
be a difference
between the repo and my WC? That's not the way I think I would see it.
If I lock a file it's then also locked in the repo; no diff there.
If someone else has locked a file in the repo I can't see that due to
the way it's
implemented now, otherwise maybe it could be viewed as a diff.
If svn:needs-lock is set, it's both in my WC and the repo, no diff.

Following the metaphore we should not implement overlays for locking.
Maybe this
would be a good starting point? Then, if during usage we find users
being very annoyed
with missing to lock files with svn:needs-lock we could alter the
metaphore to also include
displaying status of files/folders (at least for some use-cases) and
take it from there.

What do you think?

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 14 14:39:24 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.