Some wishlist ideas

[Ryan Saunders]

> > Here are a few things I'd like to see Kompare be able to do

> > that it can't right now (as far as I can tell):
> > - Partial line diffs: when only part of a line has changed, highlight the
> > actual changed part more vividly than the rest of the line
>
> Kompare already prints the characters which actually changed in bold (unless 
> more than half of the characters are different), is that not what you had in 
> mind? It might just be a matter of visualization.

Ah, ok. I didn't notice, but yes, that's what I'm talking about. ^_^ I might whip up a little extra "pretty" for visualizing the changes, at some point, and then you can tell me what you think of it. Not my highest priority item though.


> > - Mercurial integration: I'd like to be able to view the changes contained
> > in a Mercurial "bundle" file, by pointing Kompare at the bundle and at the
> > URL of the repository.
>
> This is indeed not supported yet.

This, on the other hand, _is_ my highest priority item, as I'm working on a Mercurial-based project and I need a graphical tool to help w/ code reviews. I noticed from the --help printout that you do some degree of "original file" handling:
  -o                        This will open URL1 and expect it to be diff output. URL1 can also be a '-' and then it will read from standard input. Can be used for instance for cvs diff | kompare -o -. Kompare will do a check to see if it can find the original file(s) and then blend the original file(s) into the diffoutput and show that in the viewer. -n disables the check.

...and you also have another mode for explicitly blending a diff into a filetree:
  -b                        This will blend URL2 into URL1, URL2 is expected to be diff output and URL1 the file or folder that the diffoutput needs to be blended into. 

Can you give me the 30 second overview of how blending is implemented in Kompare, and a few .cpp files that I should start out with? Then, I'll start a-hackin'.

Also, I expect that my changes will probably result in a build-time requirement on mercurial-devel...I assume that's OK?

R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kompare-devel/attachments/20110618/f16e268e/attachment.htm