SmartGit 3 EA 4 - request for better "set anchor commit"

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

SmartGit 3 EA 4 - request for better "set anchor commit"

Andrew Herron
I haven't used the EA builds in a while so I was hoping the "straight
instead of rippled lines" change in EA 3 meant you'd reverted back to the
v2 log style. Alas, it was only a minor change. I have another screenshot
if you want it - there are 2 "trunk" branches in the codebase I work on,
each currently has 3 active fix branches. "All Braches" view is hard to
follow in v2, but almost impossible in v3 :)

The new "set anchor commit" feature does make things much better in v3, but
I have two improvement requests:

   1. When anchored to a merge commit, it would be nice if both parent
   branches were highlighted (or if I was given a choice of which one to
   highlight).
      - This would be really handy when there are multiple merges (eg a
      long-running fix branch has a few merges *from* trunk during it's
      development, then eventually merged *to* trunk when complete) -
      highlighting both branches, and all merge links, would be awesome
   2. I would like an easier way to change the anchor commit
      - Ideally a mode where it automatically re-anchors as I move the
      selection through the log history
      - If you don't like that idea, a keyboard shortcut for the menu item
      would be great!

Cheers,
Andy


[Non-text portions of this message have been removed]

Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

syntevo Support
> I haven't used the EA builds in a while so I was hoping the "straight
> instead of rippled lines" change in EA 3 meant you'd reverted back to the
> v2 log style. Alas, it was only a minor change.

We never had plans to revert the layout as 3 EA results in better readable graphs for the vast majority of cases.

> I have another screenshot
> if you want it - there are 2 "trunk" branches in the codebase I work on,
> each currently has 3 active fix branches. "All Braches" view is hard to
> follow in v2, but almost impossible in v3 :)

Yes, please share that screenshot with us.

> The new "set anchor commit" feature does make things much better in v3, but
> I have two improvement requests:
>
>    1. When anchored to a merge commit, it would be nice if both parent
>    branches were highlighted (or if I was given a choice of which one to
>    highlight).
>       - This would be really handy when there are multiple merges (eg a
>       long-running fix branch has a few merges *from* trunk during it's
>       development, then eventually merged *to* trunk when complete) -
>       highlighting both branches, and all merge links, would be awesome

This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?

>    2. I would like an easier way to change the anchor commit
>       - Ideally a mode where it automatically re-anchors as I move the
>       selection through the log history

We thought about that behavior as default, but decided that it would not allow to investigate other commits when having selected an anchor commit.

>       - If you don't like that idea, a keyboard shortcut for the menu item
>       would be great!

I agree, in the meanwhile you may configure the shortcut on your own using Edit|Customize.

--
Best regards,
Marc Strapetz
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com


12/16/2011 01:40 - Andrew Herron wrote:

> I haven't used the EA builds in a while so I was hoping the "straight
> instead of rippled lines" change in EA 3 meant you'd reverted back to the
> v2 log style. Alas, it was only a minor change. I have another screenshot
> if you want it - there are 2 "trunk" branches in the codebase I work on,
> each currently has 3 active fix branches. "All Braches" view is hard to
> follow in v2, but almost impossible in v3 :)
>
> The new "set anchor commit" feature does make things much better in v3, but
> I have two improvement requests:
>
>    1. When anchored to a merge commit, it would be nice if both parent
>    branches were highlighted (or if I was given a choice of which one to
>    highlight).
>       - This would be really handy when there are multiple merges (eg a
>       long-running fix branch has a few merges *from* trunk during it's
>       development, then eventually merged *to* trunk when complete) -
>       highlighting both branches, and all merge links, would be awesome
>    2. I would like an easier way to change the anchor commit
>       - Ideally a mode where it automatically re-anchors as I move the
>       selection through the log history
>       - If you don't like that idea, a keyboard shortcut for the menu item
>       would be great!
>
> Cheers,
> Andy
>
>
> [Non-text portions of this message have been removed]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

Andrew Herron
On Friday, 16 December 2011 at 10:52 PM, syntevo Support wrote:
>  
> > I haven't used the EA builds in a while so I was hoping the "straight
> > instead of rippled lines" change in EA 3 meant you'd reverted back to the
> > v2 log style. Alas, it was only a minor change.
>
> We never had plans to revert the layout as 3 EA results in better readable graphs for the vast majority of cases.
I just don't see it. Straight lines with gaps between them are always easier to follow visually than parallel lines that angle sideways halfway along the line (particularly when the angle changes multiple times). Colour helps, but it's still slower to track the lines.

> > I have another screenshot
> > if you want it - there are 2 "trunk" branches in the codebase I work on,
> > each currently has 3 active fix branches. "All Braches" view is hard to
> > follow in v2, but almost impossible in v3 :)
>
> Yes, please share that screenshot with us.
Sure. It's only using EA 4 though:
https://skitch.com/thespyder/g1knw/smartgit-complex-comparison

> > 1. When anchored to a merge commit, it would be nice if both parent
> > branches were highlighted (or if I was given a choice of which one to
> > highlight).
> > - This would be really handy when there are multiple merges (eg a
> > long-running fix branch has a few merges *from* trunk during it's
> > development, then eventually merged *to* trunk when complete) -
> > highlighting both branches, and all merge links, would be awesome
>
> This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?
Actually yeah that's what I was trying to describe :)

> > - If you don't like that idea, a keyboard shortcut for the menu item
> > would be great!
>
> I agree, in the meanwhile you may configure the shortcut on your own using Edit|Customize.
Ah, I didn't know about that. Works great, thanks!


[Non-text portions of this message have been removed]

Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

syntevo Support
> > > I have another screenshot
> > > if you want it - there are 2 "trunk" branches in the codebase I work on,
> > > each currently has 3 active fix branches. "All Braches" view is hard to
> > > follow in v2, but almost impossible in v3 :)
> >
> > Yes, please share that screenshot with us.
> Sure. It's only using EA 4 though:
> https://skitch.com/thespyder/g1knw/smartgit-complex-comparison

I'd agree that it's not easy to follow for both versions, but I think that coloring (not layout changes) is the better way to make it easier to read.

> > > 1. When anchored to a merge commit, it would be nice if both parent
> > > branches were highlighted (or if I was given a choice of which one to
> > > highlight).
> > > - This would be really handy when there are multiple merges (eg a
> > > long-running fix branch has a few merges *from* trunk during it's
> > > development, then eventually merged *to* trunk when complete) -
> > > highlighting both branches, and all merge links, would be awesome
> >
> > This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?
> Actually yeah that's what I was trying to describe :)

We'll think about that. I guess either behavior makes sense, so we'd need some additional option for that.

--
Best regards,
Marc Strapetz
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com


12/19/2011 07:20 - Andrew Herron wrote:

> On Friday, 16 December 2011 at 10:52 PM, syntevo Support wrote:
> >  
> > > I haven't used the EA builds in a while so I was hoping the "straight
> > > instead of rippled lines" change in EA 3 meant you'd reverted back to the
> > > v2 log style. Alas, it was only a minor change.
> >
> > We never had plans to revert the layout as 3 EA results in better readable graphs for the vast majority of cases.
> I just don't see it. Straight lines with gaps between them are always easier to
> follow visually than parallel lines that angle sideways halfway along the line
> (particularly when the angle changes multiple times). Colour helps, but it's still
> slower to track the lines.
>
> > > I have another screenshot
> > > if you want it - there are 2 "trunk" branches in the codebase I work on,
> > > each currently has 3 active fix branches. "All Braches" view is hard to
> > > follow in v2, but almost impossible in v3 :)
> >
> > Yes, please share that screenshot with us.
> Sure. It's only using EA 4 though:
> https://skitch.com/thespyder/g1knw/smartgit-complex-comparison
>
> > > 1. When anchored to a merge commit, it would be nice if both parent
> > > branches were highlighted (or if I was given a choice of which one to
> > > highlight).
> > > - This would be really handy when there are multiple merges (eg a
> > > long-running fix branch has a few merges *from* trunk during it's
> > > development, then eventually merged *to* trunk when complete) -
> > > highlighting both branches, and all merge links, would be awesome
> >
> > This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?
> Actually yeah that's what I was trying to describe :)
>
> > > - If you don't like that idea, a keyboard shortcut for the menu item
> > > would be great!
> >
> > I agree, in the meanwhile you may configure the shortcut on your own using Edit|Customize.
> Ah, I didn't know about that. Works great, thanks!
>
>
> [Non-text portions of this message have been removed]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

Andrew Herron
> > > > 1. When anchored to a merge commit, it would be nice if both parent
> > > > branches were highlighted (or if I was given a choice of which one to
> > > > highlight).
> > > > - This would be really handy when there are multiple merges (eg a
> > > > long-running fix branch has a few merges *from* trunk during it's
> > > > development, then eventually merged *to* trunk when complete) -
> > > > highlighting both branches, and all merge links, would be awesome
> > >
> > > This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?
> > Actually yeah that's what I was trying to describe :)
>
> We'll think about that. I guess either behavior makes sense, so we'd need some additional option for that.Actually maybe I was a little over-reaching with that description. Here's a screenshot of what I mean - I'd like both branches to be highlighted from the selection down to the circled branch start point, and the two midway reverse merge lines as well. I don't mean highlight back to every merge ever done :)

https://skitch.com/thespyder/g11hw/anchor-commits-with-merges

This would be a huge help tracking down activity specific to a branch that has since been merged.

Cheers,
Andy



[Non-text portions of this message have been removed]

Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

syntevo Support
> > We'll think about that. I guess either behavior makes sense, so we'd need
> some additional option for that.Actually maybe I was a little over-reaching
> with that description. Here's a screenshot of what I mean - I'd like both
> branches to be highlighted from the selection down to the circled branch start
> point, and the two midway reverse merge lines as well. I don't mean highlight
> back to every merge ever done :)
>
> https://skitch.com/thespyder/g11hw/anchor-commits-with-merges
>
> This would be a huge help tracking down activity specific to a branch that has
> since been merged.

Please give the latest build a try. When anchoring a merge commit, it will include all parents:

http://www.syntevo.com/smartgit/intermediate-eap-builds.html

--
Best regards,
Marc Strapetz
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com


12/19/2011 22:40 - Andrew Herron wrote:

> > > > > 1. When anchored to a merge commit, it would be nice if both parent
> > > > > branches were highlighted (or if I was given a choice of which one to
> > > > > highlight).
> > > > > - This would be really handy when there are multiple merges (eg a
> > > > > long-running fix branch has a few merges *from* trunk during it's
> > > > > development, then eventually merged *to* trunk when complete) -
> > > > > highlighting both branches, and all merge links, would be awesome
> > > >
> > > > This should only be true for the merge commit you select as anchor itself. You don't want to follow all parents of merge commits which are in the history of your anchor commit (what would basically be the inverse of the "Mergable" commits coloring)?
> > > Actually yeah that's what I was trying to describe :)
> >
> > We'll think about that. I guess either behavior makes sense, so we'd need some additional option for that.Actually maybe I was a little over-reaching with that description. Here's a screenshot of what I mean - I'd like both branches to be highlighted from the selection down to the circled branch start point, and the two midway reverse merge lines as well. I don't mean highlight back to every merge ever done :)
>
> https://skitch.com/thespyder/g11hw/anchor-commits-with-merges
>
> This would be a huge help tracking down activity specific to a branch that has
> since been merged.
>
> Cheers,
> Andy
>
>
>
> [Non-text portions of this message have been removed]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: SmartGit 3 EA 4 - request for better "set anchor commit"

Andrew Herron
> Please give the latest build a try. When anchoring a merge commit, it will include all parents:
>
> http://www.syntevo.com/smartgit/intermediate-eap-builds.html
Oh very nice, thank you :)

[Non-text portions of this message have been removed]