KDevelop: General direction and UI - don't worry

David Nolden zwabel at googlemail.com
Mon Nov 3 22:33:38 UTC 2008


Am Montag, 3. November 2008 21:23:12 schrieb Alexander Dymo:
> I'd personally expect the finished KDevelop4 to
> 1) start fast
> 2) open any kde/cmake project from the directory on my disk without much
> question
> 3) load that project as fast as possible
> 4) compile it and compile parts of it
> 5) set a breakpoint, launch debugger and stop on it
> 6) give me code completion
> 7) rename class/method without much effort from my side
> 8) check in and out my project from any modern VCS
> etc.
> etc.

I completely forgot to respond to these technical aspects. In general you have 
quite well matches exactly what I wish too.

So let's see where we are:
1 - Is the case
2 - Not perfect yet, but in general is working
3 - I've already discussed with aleix how to achieve that by caching the cmake 
results in the duchain, and actually this has relatively high priority for 
me, since I'm tired of waiting for the project to be loaded. So I hope we'll 
have something soon here.
4 - Compiling works, yesterday aleix has checked something in to compile 
single files. Imo we need to adapt the builder a bit to leverage this 
functionality, so when we had a build-error, the first thing the builder 
tries is re-building that exact file, and then again with the full build.
5 - I hope Vladimir will come up with something soon. :)
6 - Is the case
7 - Maybe the case this evening :-D
8 - The stuff is there but I've never tried it, this probably needs a lot of 
testing

My personal addition: Documentation support integrated with the duchain, and 
konsole integration.

I've probably forgotten something, but anyway, seems like we're quite near to 
all those goals!




More information about the KDevelop-devel mailing list