Explore changesets on branch: invert changeset ordering (by default or optionally)
In the "Branch Changes" window ("View - Explore changesets on this branch"), the list of changesets is displayed in chronologically increasing order with the oldest one on top.
IMHO, it would be more consistent with the similar "View - View changesets on this branch" if the ordering was inverted so that the latest changeset was displayed on top and pre-selected. I'd think it is more common to start at the current version and work backwards through the history, as in most other views inside Plastic.
At the very least there should be a (remembered) option to invert the ordering. Personally I think the default should be "latest on top".
Göran Wallgren
shared this idea
We should certainly allow users to sort csets using their own criteria, but that being said, there’s a key reason why “explore” was implemented: to let you walk changes one by one:
http://codicesoftware.blogspot.com/2012/09/self-documented-development-through.html
-
Göran Wallgren
commented
A simple fix here would be to add a "header row" to the list of changesets. By clicking on the "header row" we could toggle the sort order of the list, just as in many other lists and tables. Or, you could simply add a small button to toggle the sort order.
-
Göran Wallgren
commented
I still really don't see why you should "dictate" the "correct" direction to traverse history. It makes this whole view less useful for users who don't use exactly the same workflow...
-
Göran Wallgren
commented
Well, I don't see why it would be illogical to want to "replay the code camera" backwards, retracing how you got to the current state. (Compare to a detective movie where video from a surveillance camera is played-back in reverse to find the moment where the recently committed(!) crime happened... ;) I still think it should be an user option to reverse the time ordering.