KDevelop 4.4.0 Beta 1 Released

After quite some downtime in the last summer weeks, the KDevelop team finally has a new release in the pipelines: KDevelop 4.4.0. Today we are happy to announce the availability of the first Beta release!

This release comes packed with bug fixes and improvements as usually. A special addition to the KDevelop experience is the new welcome page, which should make it easier for newcomers to use KDevelop and improve the workflow for existing users as well. Looking at existing plugins, we note that among others, the CMake, CVS and Patch Review plugins have seen quite some improvements.

Please test this release and give us feedback to ensure a smooth 4.4 release.


You can find the source code available to download on the KDE mirrors: Download KDevelop 4.4 Beta 1.

There, you can also find the changelogs in case you wonder what exactly has happened since KDevelop 4.3.1.

If you are a user of the Custom Buildsystem plugin, you will need to update it as well, see: KDevelop Custom-Buildsystem 1.2.2.


To verify the correctness of your downloaded packages, you can use the following SHA1 and MD5 hashes:

MD5Sum: 92ab23c7267d88819bddc73ddac23bba
SHA1Sum: 790a597b1eba9f059a1f7c9a09beb237cb79b4b0
MD5Sum: ba45caadc1a8022ef97a198ae9ef6e10
SHA1Sum: ab1c65139247f2e9744246b6fc1eb22b3bd53d51
MD5Sum: 57622fafdd148a38d6bb14301ad638c0
SHA1Sum: 1fc4d0a479d239d393edcc9bd1995fd8e5da0692
MD5Sum: 81b9374dbedf4623d2b9d5a3888b979d
SHA1Sum: 7413fda5af9e68b8f7aced89f41decd9d43dc7cf

Many thanks to the contributors who made this release possible!



OK - new core engine was updated. Well done!
But what about the Valgrind's support! We all knew that in Kdevelop v3 - it was very easy to call valgrind. NOW it is absolutely impossible! There is even no such menu item in the tool!!!
Yep, someone-somewhere even said that there is a plugin (kde-valgrind) which encapsulate desirable functionality. BUT its maintenance period has ended at the beginning of this year!!!
Voila! And now we have Kdevelop but we can't run valgrind from inside it!
WHY??? When this functionality will be rebuilded|rewritten??


In reply to by milian

Sir, did you take a deeeep look at this project?
I did, and I even wrote an e-mail to authors of this plugin and found out that the maintenance period of this plugin has been canceled at the beginning of this year! And nobody will continue the development! Plugin contains bugs - and nobody will fix them. Plugin should be adjusted imho for a new version of Kdevelop - but nobody will do that job. Voiila! We have a gigantic IDE w/o the support of profiling/memory leakage testing and etc. Or it should be more correctly to say - looks like we've got new very nice & simple !EDITOR! - but not an IDE tool ;)

Kdevelop v3 - ALREADY out-of-box! contained the support of profiling/memory leakage testing and etc. Corresponding menu items already existed there. But someone very clever have decided to remove this functionality. So - let's shout to him very loudly: "Hey! You are so clever man! Thank you! Now IDE looks much easy and.... (add another proper words by yourself)"

So. milian - if you still did not understand - we will lose very-very soon the support of profiling/memory leakage testing and etc from inside the Kdevelop tool. Soon Kdevelop only will be able to edit files and to call cmd "make|make build" and that's all...


In reply to by Anonymous (not verified)

Plus cmake integration. Plus C++ semantic browsing.

What's wrong with running valgrind from the command-line/your own script anyway? That's the easiest and most flexible way in my opinion.


In reply to by Anonymous (not verified)

cmake integration - means now editor will be able to call some command string in attached konsole. - not interesting. C++ semantic browsing - already IS a main feature of ALL existing today mature editors for programmers. But once again - a feature for an EDITORs!
The possibility to debug/profile/test created programs and features simple editor from IDE. In At v3 of Kdevelop the all things and were so. But Now we have a great editor and not more.
Will clarify why the command line is not an easiest way to work with valgrind - We can't easily to jump with one mouse click to the line of code where the problem with memory was found.


In reply to by Anonymous (not verified)


> WHY??? When this functionality will be rebuilded|rewritten??
It's sad, but if there's nobody who spends time to maintain the plugin, it must be removed. Things change, and plugins need to be adapted, and a plugin that crashes the whole application every five minutes does not do any good. You're welcome to fix the plugin! Get the sources and upload your improvements to reviewboard.kde.org.

> 1. Who decide to remove the ability to use|run the valgrind tool from inside the Kdevelop. His name - and email, pls.
It was decided collectively since it was broken.

> But once again - a feature for an EDITORs!
Clearly you're missing a key difference here between true language support and just syntax highlighting. The vast majority of time spent on writing kdevelop is used for improving language support, which means, parse stuff, provide things like quickopen, do (intelligent) syntax highlighting, and provide intelligent autocompletion. This is the core feature of KDevelop. Everything else is just a nice addition.
In fact, it's sort of the other way round than what you said: Build buttons and stuff to run external tools are found in many editors, while what really makes an IDE an IDE is its understanding for the language you're working with. That's what I feel like at least, and I think most people who like to use KDevelop do too.



In reply to by milian

1. Who decide to remove the ability to use|run the valgrind tool from inside the Kdevelop. His name - and email, pls.
2. Why it was decided to do this.
3. Does anyone from KDE.org Bosses have a plans to return back this functionality NB! already existed in previous version of Kdevelop. If no - why?
4. Where we can find the !complete list! of removed (in comparison with v3.) features in Kdevelop v4.
5. IF you will insist that the support of valgrind should be done only via the plugins system - who will be responsible for maintaining this plugin in up-to-date conditions? His name - and email, pls.


In reply to by Anonymous (not verified)

Does anybody know answers on asked questions?

Nice Beta so far. Thanks a lot for developing this great project.