Steve wrote:
> Do we really need these?
No, not really :-)
> I was never really happy with the current
> implementation because I just can't see why we need to make every
> little thing configurable. I mean, TSVN is a *GUI* client, and users
> should expect to close a dialog at the end of an operation.
>
> I'd vote for one simple option "Don't close on errors". If the dialog
> closes on conflicts/merges/etc. and the users thinks "I'd wanted to
> see that!" then I'd recommend to _not_ close the dialog automatically.
I can live with the simple option, but I'd like to have the combobox. Maybe
I'm overdoing it here, but since the "out of date" error and maybe others
have moved to the progress dialog I'd like to have this more configurable.
Currently we have two gui elements that allow us to configure three options.
I'm voting for one gui element that allows us to configure three or four
options.
My personal preference (lazyness) is:
- I don't want to close the dialog after an update when there are only blue
lines (90% case)
- I want to see the dialog when conflicts (3%)
- or errors occured (2%)
- I'd like to keep the dialog open when merges have taken place (5%)
That's why I vote for the combobox.
Just checked what TortoiseCVS is doing. They've got a combobox with the
following three options:
- close manually
- close if no messages
- close if no errors
Cheers
- Lübbe
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Feb 10 10:35:43 2005