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

Re: Feature request

From: Nick Lindridge <nick_at_ioncube.com>
Date: 2007-02-25 17:50:34 CET

Hi Stefan

> Ok, I don't understand. What's the big difference between a single click
> and a doubleclick? I really don't think that a single click is faster
> than a doubleclick?
> (you know that you can doubleclick on the files in the commit dialog to
> diff them?)

I know, I mentioned this. When checking in, I'll generally either diff a
file in Explorer and then commit, or select commit and select the diff
from there with the double click. For one file this is fine, but when
there are multiple files it's quite time consuming and non-optimal. This
is one reason why the suggestion of being able to record commit comments
at the point of deciding to make the change, rather than retrospectively,
could be advantageous. I also like that idea because it seems more natural
to me for a sequence of events to be 1) decide to make a change, 2) note
that the change is going to be made, 3) implement the change, as opposed
to 1) decide to make a change, 2) implement the change, 3) use diffs to
work out what was changed. This can lead to vague and even inaccurate log
messages, with commit messages applied to more files than were truly
affected by a change or useless messages. So this is one thing.

My thoughts about an apply button on the commit dialog and perhaps a
commit/diff dialog were to make the existing process of adding commit
messages quicker. I will typically have a bunch of files to commit, I want
to commit them all, I do not want to give each one the same message, and I
do want to give them a decent message. Rather than going to explorer to
pick off files one by one, I'd like first to do a commit on the root
folder so that all files are picked up just like now. The next step would
be to easily and quickly see diffs of selected files within the same
dialog as this is quicker and less distracting than having dialogs popping
up that have to be closed (which is more mouse movement and clicks), and
then to be able to enter a message and commit with the message applied to
one or more files. The dialog would stay open until all files were
committed or it was cancelled. Even for people not running diffs but
entering different log messages, the process would be quicker than it is

An alternative to having one dialog with a diff, changed files list, log
message text and recent messages, is to have separate non-modal dialogs
that are linked. In this case there might be commit dialog with either a
list or tree of changed files on the left, and a recent messages and log
text field on the right, one above the other. A diff window could be
popped up separately if required, and that would update automatically
based on the file selected (with a single click) from the list/tree. The
disadvantage here is that unless running two monitors, it's likely that
that the user would have to keep alternating between bringing the diff to
the front and the commit dialog to the front.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Feb 25 17:51:13 2007

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.