Review Request: Kompare integration in KDevelop to review patches and vcs differences

David Nolden zwabel+reviewboard at gmail.com
Wed Aug 12 09:36:21 UTC 2009


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/1284/#review1996
-----------------------------------------------------------


As we talked, this should be integrated in the patch-review plugin. The patch should first be handed to patch-review, and then patch-review should open the kompare document.

I would suggest that the kompare part would be only one tab with the title "Overview" which should contain all the changes together, and all the affected documents should be opened in editor tabs with the changes highlighted by patch-review.

- David


On 2009-08-11 16:19:12, Aleix Pol wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviewboard.kde.org/r/1284/
> -----------------------------------------------------------
> 
> (Updated 2009-08-11 16:19:12)
> 
> 
> Review request for KDevelop.
> 
> 
> Summary
> -------
> 
> This adds a new PatchDocument and a IPatchDocument interface that lets us work with patches integrating them using the Kompare part.
> 
> It adapts that to the Vcs support so that we can review local changes. (not complete support of all the VcsDiff cases)
> 
> There is more work to do still, but I wanted you to see what's been worked one and to criticize it if needed. Now when you compare to base you're moved to the Test area (which should be renamed to Review area, imho) and opens there all the different files. One document per changed file.
> 
> The compilation when the KomparePart is not installed is not really sorted out yet, I'll add that on a next version of the patch.
> 
> Some work will be needed on the KomparePart as well. Now when we compare a file with a string, Kompare assumes the new one is the string and in our case it's not (it's the string that comes from the VCS support).
> 
> We should make it possible to specify the base directory when working with 1 patch.
> 
> 
> Diffs
> -----
> 
>   /trunk/KDE/kdevplatform/interfaces/idocumentcontroller.h 1009258 
>   /trunk/KDE/kdevplatform/shell/CMakeLists.txt 1009258 
>   /trunk/KDE/kdevplatform/shell/documentcontroller.h 1009258 
>   /trunk/KDE/kdevplatform/shell/documentcontroller.cpp 1009258 
>   /trunk/KDE/kdevplatform/shell/partcontroller.h 1009258 
>   /trunk/KDE/kdevplatform/shell/partcontroller.cpp 1009258 
>   /trunk/KDE/kdevplatform/shell/partdocument.h 1009258 
>   /trunk/KDE/kdevplatform/shell/partdocument.cpp 1009258 
>   /trunk/KDE/kdevplatform/shell/patchdocument.h PRE-CREATION 
>   /trunk/KDE/kdevplatform/shell/patchdocument.cpp PRE-CREATION 
>   /trunk/KDE/kdevplatform/vcs/vcspluginhelper.cpp 1009258 
> 
> Diff: http://reviewboard.kde.org/r/1284/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Aleix
> 
>





More information about the KDevelop-devel mailing list