Merge conflict dialogue is the biggest crap ever
42 views
Skip to first unread message
swis...@gmail.com
May 4, 2018, 7:39:53 AM5/4/18
to TortoiseSVN
For many years now I am forced to use Tortoise for working with SVN server. Everybody in my team is afraid of tree conflicts, since the support of Tortoise for such conflicts is absolutely horrifying. You will never know what actually happens and it is very frequent, that all your changes are lost.
The dialogue window does not tell you what happened, it does not tell you what is going to happen which you press this or that button. It is actually one of the best examples I have ever soon of how you should NOT design and label a usear dialogue box. The worst thing is that this has not improved over years and generations of programmers are losing their changes because of that. I am very disapponted with tortoise.
The dialogue window does not tell you what happened, it does not tell you what is going to happen which you press this or that button. It is actually one of the best examples I have ever soon of how you should NOT design and label a usear dialogue box. The worst thing is that this has not improved over years and generations of programmers are losing their changes because of that. I am very disapponted with tortoise.
Stefan
May 4, 2018, 7:43:13 AM5/4/18
to TortoiseSVN
Thanks for your insightful and nice comment about the UI.
We're flattered by your comments and your many compliments.
We're flattered by your comments and your many compliments.
chuck...@gmail.com
May 4, 2018, 11:02:37 AM5/4/18
to TortoiseSVN
On Friday, May 4, 2018 at 1:39:53 PM UTC+2, Martin Widmer wrote:
> For many years now I am forced to use Tortoise for working with SVN server. Everybody in my team is afraid of tree conflicts, since the support of Tortoise for such conflicts is absolutely horrifying. You will never know what actually happens and it is very frequent, that all your changes are lost.
> The dialogue window does not tell you what happened, it does not tell you what is going to happen which you press this or that button. It is actually one of the best examples I have ever soon of how you should NOT design and label a usear dialogue box. The worst thing is that this has not improved over years and generations of programmers are losing their changes because of that. I am very disapponted with tortoise.
Leaving aside the tone, I'm confused. I assume you're referring to the new dialog in 1.10? Or have you not updated yet? Since you say "it has not improved over years", it sounds like you haven't.
> For many years now I am forced to use Tortoise for working with SVN server. Everybody in my team is afraid of tree conflicts, since the support of Tortoise for such conflicts is absolutely horrifying. You will never know what actually happens and it is very frequent, that all your changes are lost.
> The dialogue window does not tell you what happened, it does not tell you what is going to happen which you press this or that button. It is actually one of the best examples I have ever soon of how you should NOT design and label a usear dialogue box. The worst thing is that this has not improved over years and generations of programmers are losing their changes because of that. I am very disapponted with tortoise.
In the case of 1.10, I actually find the new UI to be quite an improvement. SVN 1.10 put some work into making interactive tree conflict handling more useful, and TortoiseSVN shows a proper dialog for that.
There are issues with the new dialog (cf. my recent thread about this), but I think it's a step in the right direction.
Reply all
Reply to author
Forward
0 new messages