4 ms·
Disclaimer. I'm the creator of GitSense which is working on building advanced power tools for Git and GitHub. The diffing problem is solved quite easily with
by sdesol 13y ago
Disclaimer. I'm the creator of GitSense which is working on building advanced power tools for Git and GitHub.
The diffing problem is solved quite easily with the Google Diff, Match, Patch algorithm and our Smart View technology. When GitSense was created, it was obvious that we all work differently and we all have different needs which was why we made it insanely customizable. If you are not familiar with the Google Diff, Match, Patch algorithm, you can learn more about it here:
https://code.google.com/p/google-diff-match-patch/ https://code.google.com/p/google-diff-match-patch/
I've also put some screen shots of what the diff results for two markdown files would look like at:
http://screenshots.gitsense.com/google-diff-patch-match.html http://screenshots.gitsense.com/google-diff-patch-match.html
The context aware source code that is used in GitSense to display the diff can be found here:
http://screenshots.gitsense.com/google-diff-match-patch-integration.js http://screenshots.gitsense.com/google-diff-match-patch-inte...