Linked by Thom Holwerda on Mon 3rd May 2010 13:47 UTC, submitted by Andreas Andersen
KDE "The KDevelop team is proud and happy to announce that KDevelop 4.0 is finally available as stable release. KDevelop comes with lots of innovative features, even though many features from the 3.5 series were dropped due to a nearly complete rewrite. In particular the developers have focused on building an excellent C++ IDE instead of trying to integrate lots of languages and features halfheartedly. Of course KDevelop 4 also builds an excellent basis for other languages, the best proof for that is the PHP plugin that is released alongside KDevelop 4.0. KDevelop 4.0 has an excellent C++ code understanding engine, which allows the IDE to understand your code better than you do, and which is then used to assist you by releasing you from tiresome tasks."
Permalink for comment 422430
To read all comments associated with this story, please click here.
RE: And QtCreator ?
by MORB on Mon 3rd May 2010 17:17 UTC in reply to "And QtCreator ?"
Member since:

I've tried both and used both for a while.

I'm working on a project that is part c++ part javascript, using cmake, with some files in a custom interface definition language used to generate javascript bindings.

It's a bit of a mess, and it doesn't fit well in qtcreator, because when you import a cmake project into it, it inserts only the c++ files referenced by the build into the project tree and ignores everything else (the js files, the idl files, heck even the todo file I have lying around).
For some reason they deemed necessary to display only a subset of the directory tree of the project gathered from the cmake files, instead of just the entire directory tree of the project.
I don't understand why they don't do that, it's not like people have projects lying around in directories full of unrelated stuff.
If it's in the project directory tree, then it's part of the project.

Now kdevelop 4 impressed me because despite the hybrid nature of my project (c++, javascript, and my own little idl language), everything just works. I can see all my files in the tree, and code completion works rather well, despite that my code contains a lot of C++0x things that kdevelop doesn't know how to handle yet, as well as a lot of templates.

It even manage to color my idl files almost properly out of the box simply because they look like a subset of C++, even though they don't even use an extension that's anywhere usual for a c++ file.

There are lots of nice goodies. It hilights the symbol under the cursor everywhere in the code, it automatically assign a unique color for each function parameter name, local variable names and members.

It's pretty nice overall.

QtCreator has a lot of the same shortcoming as visual studio: it's pretty much really designed for projects created in the ide, the way the ide wants it. Basically it's fine if what you want to do is a standard, qmake-based qt project, which is I guess exactly what trolltech needed it to be.

kdevelop on the other hand seems to make a lot of effort to work with what you throw at it.

Edited 2010-05-03 17:20 UTC

Reply Parent Score: 4