Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add three columns for code #54

Open
todatamining opened this issue Feb 8, 2019 · 4 comments
Open

Add three columns for code #54

todatamining opened this issue Feb 8, 2019 · 4 comments

Comments

@todatamining
Copy link

todatamining commented Feb 8, 2019

column1 --------------------------column2 ------------------------------------------column3
code in commit1..................code in commit2........................................change in commit3

currently, only code in commit2 is shown. It is hard to know what has been changed or changed to exactly.

@todatamining todatamining changed the title Is it possible to show three columns? Add three columns for code Feb 8, 2019
@pomber
Copy link
Owner

pomber commented Feb 9, 2019

Not sure about this one. One of the things people like about this tool is that there isn't too much noise.
#63 will add a link to GitHub commit where you can see the diff, maybe that's enough, or maybe we can add a special diff view later.

@shayanb
Copy link
Contributor

shayanb commented Feb 10, 2019

I agree. The minimal view is really clear and perfect for finding the diffs. The url to the actual commit can help to investigate the details and change log.

@pomber
Copy link
Owner

pomber commented Feb 21, 2019

From #22

The current visualization is more for browsing different versions of a file rather than viewing the diff between two versions. I want to keep that, but I agree that people usually want to see a diff after browsing the history.
I'm thinking on adding some way to activate a "diff mode" that animates between diffs, as you change the "left" and/or the "right" version of a file.

@katrinleinweber
Copy link

How about only 2 columns? git-temporal does this. Would that be a good compromise between the 2 use-cases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants