VCS Project integration plugin

[Niko Sams]

Hi,

I get this crash when executing Save As... for a file:
Thread 1 (Thread 0x7f150cecc760 (LWP 23145)):
[KCrash Handler]
#4  0x00007f14e70ce530 in VcsProjectIntegrationPlugin::changes
(this=0x5072e80, project=0x0, urls=@0x7fff262dc9d0,
mode=KDevelop::IBasicVersionControl::NonRecursive)
    at /home/niko/kdesvn/kdevelop4-extra-plugins/vcsprojectintegration/vcsprojectintegrationplugin.cpp:132
#5  0x00007f14e70ce838 in VcsProjectIntegrationPlugin::documentSaved
(this=0x5072e80, document=0x451b6a0)
    at /home/niko/kdesvn/kdevelop4-extra-plugins/vcsprojectintegration/vcsprojectintegrationplugin.cpp:103
#6  0x00007f14e70cd5d7 in VcsProjectIntegrationPlugin::qt_metacall
(this=0x5072e80, _c=QMetaObject::InvokeMetaMethod, _id=2,
_a=0x7fff262dcb10)
    at /home/niko/kdesvn/build/kdevelop4-extra-plugins/vcsprojectintegration/moc_vcsprojectintegrationplugin.cpp:83
#7  0x00007f1509960296 in QMetaObject::activate () from
/usr/lib64/qt4/libQtCore.so.4
#8  0x00007f150c68fc3d in KDevelop::IDocumentController::documentSaved
(this=0x87f3b0, _t1=0x451b6a0) at
/home/niko/kdesvn/build/kdevplatform/interfaces/idocumentcontroller.moc:230
#9  0x00007f150c68c600 in KDevelop::IDocument::notifySaved
(this=0x451b6a0) at
/home/niko/kdesvn/kdevplatform/interfaces/idocument.cpp:69
#10 0x00007f150c3d86ce in KDevelop::TextDocumentPrivate::documentSaved
(this=0x4fafea0, document=0x7ef1a70, saveAs=false) at
/home/niko/kdesvn/kdevplatform/shell/textdocument.cpp:181
(Using git)

I actually like the idea of having a separate toolview - it's like a
"git status" toolview.

Issues I had:
- it doesn't update always
- there is no refresh button to update manually

suggestions:
- use the file context menu
- double click should show the diff or whatever is relevant to the change


Niko

On Mon, Aug 23, 2010 at 20:30, Aleix Pol <aleixpol at kde.org> wrote:
> Hi,
> I revived that plugin I was working on during the last KDevelop meeting, now
> it's a new toolview that displays what changes we have in every project we
> have opened. It's quite useful to be able to see what's the work we have.
> The only very important thing to put is a context menu to expose some
> important actions.
> It still needs some love so I won't push it for 4.1 but I think it can be a
> good thing to have in 4.2. If you have any interest on that please test it
> and tell me what do you think.
> Cheers!
> Aleix
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>