= Ideas for improving the changeset view

== User Interface

=== Current Status

Pretty stable across all Trac releases, for example our changeset:17 in: 
[/demo-0.11/changeset/17 0.11], 
[/demo-0.12/changeset/17 0.12],
[/demo-0.13/changeset/17 0.13]

Here's how the same changeset look in other systems:
[https://github.com/edgewall/trac/commit/461956be66fd46f14979ba471ff36de1b369c1c9 github],
[https://bitbucket.org/edgewall/trac/changeset/16 bitbucket] and here are some different changesets in: [http://gitorious.org/git-plugin/git-plugin/commit/ce3bd8b5f7eb7a847ebd36f1905781cf02106e97 gitorious] and [http://www.redmine.org/projects/redmine/repository/revisions/6130 Redmine] /
[https://www.chiliproject.org/projects/chiliproject/repository/revisions/e311b26c414c8941c5c83caba9f250d72f896c0f ChiliProject],
[http://code.google.com/p/tracshell/source/detail?r=70# GoogleCode],
[https://fisheye2.atlassian.com/changelog/python?cs=80004 FishEye].


=== Convergence

The links on the file entries at the top currently directly lead to the file browser and only the (diff) links get you to the actual diff. I think we should reconsider this choice as in github and bitbucket the file entries link to the diff instead.

An alternative would be to directly inline the changes below the path, #515 (as done in !FishEye and Gitorious for example).

The Redmine/!ChiliProject way of showing the tree is also interesting, but having the diffs on a separate page is not.


=== Related tickets
Most ERs concerning the "version control/changeset view" probably apply:
[[TicketQuery(status=!closed,component=version control/changeset view,type=enhancement)]]

The bugs are more about the generation of the changesets ( [[TicketQuery(status=!closed,component=version control/changeset view,type=defect,format=compact)]]) and are not so relevant for the user interface except: [[TicketQuery(id=5549)]]