-
Anjuta or Kdevelop
I have always used Kate and gcc whilst learning C++ on my Linux boxen, however I now want to move into an IDE.
One of th late editions of LinuxFormat magazine tested many programming IDE's and Anjuta got 9/10 and Kdevelop got 10/10.
As there is not much in it, I was wondering if anyone on here has a good deal of experience with the 2 and can offer some advice as to which may be the better out of the 2 to work with.
To give a little insight into my ideals, I hate VC++ and I love Dev-C++.
-
I've done a very small amount of work in KDevelop. It's not bad really. I think its better that DevC++ actually and somewhat similar. These days vi is kind of a requirement for me though so I just got used to using it exclusively.
I have to raise an eyebrow at your comment about VC++ though. I find it to be the most fully functional IDE out there. It also has the best debugger environment I've ever seen. You can say that the compiler itself is not that good and not standard compliant but the IDE is superb.
As for KDevelop. highly configurable. thumbs up if you want an IDE on *nix.
-
I to echo support for KDevelop. It was pretty weak awhile ago when it was still in the 1.x and early 2.x stages, but it has grown well enough that I have to say that it is my favorite IDE period at its current release : v.3.0.3 . The only problems I find with it are some miscellanious problems, such as:
1) the code completion/suggestion system could use quite a bit more work, as this is one thing where it falls short of MSVC. Also, if you use inheritance, I notice that it wont include the inheritted members of the class in the code suggested popup.
2) drawing off what FYB said about debuggers, it also falls short here compared to MSVC. I have noticed that the debugger sometimes wont save any changes you make in the code while using the debugger, leaving you to redo whatever you had done before.
3) file extension based syntax highlighting : I am not sure if it just me, but when you define new types of files, such as a *.imp file for template implementation, and attempt to set the editor's(both the advanced and QT editor) highlighter template, that it will always highlight it as if it were a normal text file.
On the upside however:
1) It is free, and for the cost I can say it sure beats MSVC :p
2) if one has to work with linux all the time in programming, KDevelop would have to be the way I would suggest doing it. It makes the whole programming experience hassle free when you dont have to worry about if you forgot to arrange your makefile properly and dont have to manually edit it everytime you just want to add another file.
3) also as FYB was saying : The customizability of KDevelop is darn extensive. You can pretty much switch everything around that you would want to , and if there is something you can't, write up a plugin for it.
In the end, this was a battle between MSVC and KDevelop, as Anjuta is still far away from becoming an appropriately robust IDE to make you want to use it instead of vi and gcc, and in the end KDevelop wins IMO due to its extensive customizability, robust feature list, and its price.
hope this was helpful
-
Very helpful.
Thanks guys, I know which route I'll be going down now.