2009/4/1 void pointer <rcdailey_at_gmail.com>:
> On Wed, Apr 1, 2009 at 4:58 AM, Simon Large
> <simon.tortoisesvn_at_googlemail.com> wrote:
>> One thing you have not considered is that the choice may depend not
>> only on the dialog in question but also on the repository access
>> method. One reason for keeping the dialog open is to see what is
>> happening over a slow internet connection (like tigris.org), and
>> seeing a definite "Finished" rather than just the absence of a
>> progress dialog. OTOH repositories accessed via the LAN will have a
>> very much faster response, in which case you would likely only want
>> the progress dialog to show errors. To cope with that you would need
>> per-project settings, but implemented per-user, not using subversion
>> properties which are forced on every user. So even the fine-grained
>> per-dialog solution you proposed is not going to meet all
>> requirements. We need to keep this simple.
>
> I'm not sure what you are trying to say here. Regardless of your bandwidth,
> if the dialog disappears then I can safely assume (at the very least) that
> no errors occurred.
>
> As far as a commit goes, this is all I care about. I
> don't really care about each individual step. And besides, if the progress
> is really going to take that long due to bandwidth then I must have plenty
> of time to watch the progress since the dialog wouldn't be closing anytime
> soon. Perhaps I am misunderstanding what you are saying?
If I am on a slow connection a commit might take an hour. I am not
going to sit and watch it, but I do want to know when it is finished,
and a dialog which says "Finished" is a better indicator than the
absence of a dialog (as a kid did you ever play that game where there
is a tray of objects and then someone takes one away while you're not
looking? Spotting absence is a lot harder than spotting presence).
Anyway, I start the commit and then go off to a long meeting. When I
get back there is no dialog and all the icon overlays are still red
(because they don't auto-update). Did I start that commit rolling
before I went into the meeting or not?
Of course it is very easy to check that, but in the same way it is
very easy to hit OK or ESC to dismiss the progress dialog. People have
very different preferences; the set of options you have suggested
scratches your itch, but other people may have different itches which
would require another completely orthogonal set of options.
Anyway, I think we will have to agree to disagree. If you're happy
with the method I proposed then we can look at that but the ultimate
flexibility options are just not going to happen.
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=1510742
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-01 23:04:44 CEST