On 10/2/07, Stefan Küng <tortoisesvn@gmail.com> wrote:
>
> On 10/1/07, Joel Chen <whitegust@gmail.com> wrote:
>
> > First, I would like to thank you guys for making such a great front-end
> for
> > Subversion. It has helped my work tremendously! Second, I have few
> > suggestions for TortoiseSVN.
> >
> > I suggest that TortoiseBlame and TortoiseMerge be combined together.
> This
> > way we would have greater sight on overall changes. I had read about the
> > Merge Tracking on the upcoming Subversion 1.5. It would be nice when
> > TortoiseBlame and TortoiseMerge work together along with Merge Tracking.
>
> What does blame has to do with diff? How would you combine those
> completely different and unrelated tools? What would be the connection
> between those two?
> What would you gain by this feature?
Hi Stefan, sorry to have caused much trouble to you with my suggestions. My
thoughts were to have a view of who modified which lines and when in
TortoiseMerge, so that developers can check who last modified a particular
line when merging.
> Further suggestion I have is for TortoiseSVN become more
> developer-friendly.
>
> Great! In case you haven't noticed: we're developers too.
>
> > Currently in TortoiseMerge I can only copy text from the left pane to
> the
> > right pane. It would be more developer-friendly when it could be done
> > vice-versa. A great merge tool for reference is WinMerge, available at
> > http://winmerge.org.
>
> There's a button/menu entry which lets you swap the left and the right
> file.
Yes, this swap button is good feature, but I would prefer to be able to copy
text from both sides.
> Now we can compare revisions with 2 or more revisions apart by selecting 2
> > revisions in the Revision Graph, or compare working copy with another
> > revision through right-click in the Log Messages, or selecting 2
> revisions
> > in the Log Messages and compare them. Hence, Log Messages seems to have
> more
> > control in comparing revisions than Revision Graph which is quite
> ironical.
>
> You're statement is correct. But what's your point?
> Keep in mind thought that the revision graph is a *graph* and not a
> tool to work with. For most projects, it simply takes too long to even
> show the graph - the log dialog is faster and should be used for
> anything else than showing a graph.
Okay, now I see that your graph is aimed to be graphical and consists of
rendering symbols and texts at the moment. The rendering could be what's
causing a long time to display. That's a major drawback of the graph.
Correct me if I'm wrong.
> I had read that the Repository Browser will become Explorer-like in the
> > coming version of TortoiseSVN. For developer-friendliness, I suggest
> > changing the Revision Graph to become Explorer-like with full revision
> > comparison functionality for better viewing and easy navigation. There
> would
> > be 2 modes of view, mode 1 is files(parent) and revisions(child), mode 2
> is
> > revisions(parent) and files(child).
>
> As my grand grand father used to say: Hää???
>
> Since when can explorer show a graph?
> I'm starting to wonder if you even know how the revision graph is
> generated or what it actually shows you? You know that it doesn't show
> you the same information as the log dialog?
My idea is to have a revision tree instead of a revision graph. A tree view
to organise all the connections in the graph.
Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
Thanks for your efforts in making TortoiseSVN so professional!!
Cheers!
Joel
Received on Tue Oct 2 15:08:48 2007