On 10/19/07, Stefan Küng <tortoisesvn@gmail.com> wrote:
> On 10/19/07, Alexander Klenin <klenin@gmail.com> wrote:
> > I agree that clutter should be reduced.
> > However, I think wizard interface is not the answer, as it forces
> > some unnecessary and arbitrary decision order.
> > In particular, I strongly dislike an idea that each time user requests a merge,
> > he must answer some question *before* he can proceed.
>
> Aehem: you *always* have to fill in the url and revisions for the
> merge before you can proceed. Whether you enter them on one dialog or
> two shouldn't really matter.
Well, there are already three dialogs involved --
merge dialog, repo-browser to select URL and log dialog to select revision.
Adding yet another step will definitely hinder at least my workflow.
> > I perform about a dozen merges daily at work, it would certainly be
> > very annoying.
> What kind of merges are those? Merges of trunk to your branch? Then
> use the "Merge All" command.
No, they are the other way around -- I, as a project manager,
merge topic branches into trunk
(and sometimes from one trunk to another one, in a cross-project merge).
At the moment, I can not imagine a workflow that requires frequent merges
from trunk to branch.
> > How about tabs control?
> Yuck! Way too ugly.
Hm, what prevents us from making it beautiful? ;-)
Tabbed interfaced are popular these days.
> And that doesn't help *guiding* the users.
Well, it will, on the one hand, hide rarely-accessed info from
unexperienced users,
and, on the other hand, would not require those who already learned a tool
to do unnecessary extra work.
--
Alexander S. Klenin
Insight Experts Ltd.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 19 10:17:33 2007