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

Re: Another auto-close idea...

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Wed, 1 Apr 2009 22:12:33 +0100

2009/4/1 Stefan Küng <tortoisesvn_at_gmail.com>:
> void pointer wrote:
>> On Wed, Apr 1, 2009 at 4:58 AM, Simon Large
>> <simon.tortoisesvn_at_googlemail.com
>> <mailto:simon.tortoisesvn_at_googlemail.com>> wrote:
>>
>>     I am beginning to see where you are coming from now, and my suggestion
>>     is to compromise between your requirements for fine-grained control
>>     and Stefan's requirement for simple UI. How about having two drop down
>>     lists, one to handle the cases where remote changes will affect my WC
>>     (update, switch, merge) and one to handle the cases where my WC is
>>     only affected by what I am doing locally, even if it involves remote
>>     access (add, revert, commit). The remote list would have all the
>>     current options except (obviously) the local change one. The local
>>     list would have 3 options: close manually, auto-close for local
>>     operations (i.e. not commit) or auto-close if no errors.
>>
>>
>> This sounds like an acceptable compromise. I'd be happy with this.
>
> I think the local option only needs a checkbox: autoclose for local
> operations. We never auto-close on errors - an error is important
> information and must be shown to the users. Otherwise we would get
> flooded with confusing bug reports...

I don't think anyone is suggesting we ever do auto-close if there are
errors. My 3 options are:

1. Close manually (never auto-close)
2. Auto-close for local operations only (unless there are errors)
3. Auto-close for all operations (unless there are errors)

Remember that these only apply to operations which do not pull down
changes from the repository, and there is never an auto-close if there
are errors.

Option 2 will auto-close for Add, Revert and other local operation
which do not contact the repository. It will not auto-close for
commit.

Option 3 will auto-close for Add, Revert and other local operations,
and for Commit too.

Commit is in no-mans-land; it contacts the repository, so I might want
to see progress for slow connections, but it will not do anything
unexpected to my WC, so Robert (void pointer) wants it to auto-close.
That's the reason I want to keep all 3 options.

I know, I'm going to have to document this somehow ...

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1510835
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-01 23:12:44 CEST

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.