"KDevelop is the premier Free integrated development environment. The project is currently working towards KDevelop 3.4 with a bunch of new features and a major new version KDevelop 4. To find out what's coming up in one of KDE's most important projects KDE Dot News spoke to three of the authors about their current work and future plans."
Post a Comment
Member since:
2006-01-31
Member since:2006-05-13
It is on the additional plugins list http://monodevelop.org/Development_Roadmap
I would love to see/use it, but recon it just doesn't have such a priority.
Back on topic, KDE isn't really my camp, but KDevelop is just one fine peace of software. Kudos and keep up the good work =)
Member since:2006-01-31
Member since:2005-07-06
KDevelop starts up with 27 toolbar buttons and 24 tabs.
http://www.kdevelop.org/graphics/screenshots/3.3/tracing2.png
Netbeans starts up with 18 toolbar buttons (up to 25 if you enabled the profiling support) and six tabs.
http://www.bfeeney.uklinux.net/images/netbeans5-java6.png
Visual studio starts with more toolbar buttons, but a lot less tabs.
http://en.wikipedia.org/wiki/Image:Vs2005.screenshot.png
Ultimately, it's harder to find your way around KDevelop than it is around the other major IDEs, simply because it's laid out in a poorer manner. I used Delphi a lot at work: when I tried out KDevelop I was horrified at how complex it was. In particular the amount of tabs is awful, you can find yourself searching all over the place for simple things.
This is not bloat, incidentally (that refers to resource usage), but it is poor user-interface design. KDevelop is a great Unix IDE, the fact that it can setup all those autoconf/automake scripts for you is a huge bonus, but the UI does need attention. Fortunately, one of the developers on the do mentioned that they're doing just that.
Member since:2005-10-13
This is not bloat, incidentally (that refers to resource usage), but it is poor user-interface design.
Exactly. There is a huge difference between the two, but a lot of people just use "bloated" to describe pretty much anything they don't like.
It could use some UI work, and hopefully that will be done. It sounds like code completion is getting a lot of work done on it as well, which was needed pretty badly.
Member since:2005-07-06
Member since:
2006-02-25
Member since:
2005-08-31
I've been using KDevelop for every day C++ developing, for several years now. Congrats to the KDevelop team for their hard work, its progress is great in some areas (debugging, vcs) and quite broken in others (code completion/generation, context help). There are a couple of things I would love to see added or improved, some of them are work in progress, others maybe already exists... only a wishlist 
- Refactoring
- Better code formatting support (specifically on automatic method definition)
- Better template/class generation support, document $VARS (author, project, file...), add simple macros for manipulation (concat, upper, split, replace, path, ext...).
- Split window view, header and source, synchronized class explorer
- Better source code context help (say, using std::cout; cout.flush(); will show std::ostream::flush doxygen reference, on help window or tooltip)
- Remember detached tabs, position and size (specifically on debugging)
- Custom variable inspecting (specifically STL classes: show std::string as "string", std::vector<std::string> as "{ "string", "string" }")
- Specify directories: header and implementation (and file switch, method completion, debugging still working), templates, scripts (bootstrap...), per project or target.
- Specify make target.
Member since:2005-07-06
