Kate/KDevelop October Sprint: What's new in KDevelop
This is the second part of the article on the joint Kate/KDevelop development sprint that took place in Vienna from the 23rd to 29th of October this year.
If you are interested in some background and what has happened in Kate-land during the sprint, make sure to read the first part of this article . This issue will give an overview over the interesting changes in KDevelop.
Many thanks here once more to the KDE e.V., its sponsors and donors  and the Join The Game crowd  for funding the development sprint. Special thanks go to Joseph Wenninger  for not only organizing the sprint but also funding parts of it. And finally thanks again to Vivid Planet  for inviting all attending developers to a great dinner.
: http://dot.kde.org/2012/11/24/katekdevelop-october-sprint-whats-new-kate  http://ev.kde.org/getinvolved/supporting-members.php  http://www.jowenn.net/  http://www.vivid-planet.com/ : http://jointhegame.kde.org/
What's new in KDevelop
The attending KDevelop hackers have been very busy and productive during the sprint. About 550 commits have been made in just one week. They address performance issues, fix bugs, polish our user interface or integrate new features. In the following you will read about most noteworthy changes that have been made.
While Miha Čančula sadly could not attend the development sprint, he worked quite hard in the months before. One thing he worked on was a framework for Unit Test integration for KDevelop. This allows you to quickly run and debug the unit tests of your projects directly from KDevelop. Make sure to read his report  on the new testing framework.
During the sprint we sat together and did a final review of ths work and merged the unit test support into our development branches. Afterwards, Niko and Aleix where busy polishing the newly merged code and greatly improved and stabilized it. As with the rest of the KDevelop codebase, this new framework is easily extensible through plugins. Currently we have support for CTest/QTestLib and PHPUnit, while support for Ruby's Test::Unit is in the works.
[image: testing.png title:Unit Test Integration]
Unit test support was something that Miha worked on in his spare time. This year he was also a GSOC student  for KDevelop: He worked hard on an improved project templates support and - more importantly - wrote a new Grantlee based "file template" feature. This allows you to create snippets for new files which replaces and extends the existing "Create new Class" wizard we had in KDevelop up until now. Make sure to read his final GSOC report on the matter .
As usualy, you can create a new class, but there are now special templates for extended semantics and frameworks. This allows you for example to create C++ classes following the PIMPL idiom or which implement the Qt shared value semantics. But we also have file templates for GObject classes, PHP classes, CMake modules, etc. pp.
All this work was also finally merged into master during the sprint in Vienna. Aleix and Milian polished the implementation, while Alexander and Miquel created proper Ruby file templates. The good thing is that you can create your own templates  and share them with your colleagues or other KDevelop users. If you wrote a good general purpose template, you could also sent it to us and we'll include it with the rest of the existing examples.
[image: filetemplates.png title:File Templates]
: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/noughmad/37002 : http://noughmad.com/2012/08/19/gsoc-templates-in-kdevelop-final-report/ : http://techbase.kde.org/Projects/KDevelop4/File_template_specification
While Sven did not only work on his pet project, the Python language support, he sure managed to improve it a lot. He concentrated on code optimizations, clean ups and most importantly bugfixes. This paved the way for the first beta release  of kdev-python 1.4. Just shortly after the sprint then he successfully released kdev-python 1.4  which works together with KDevelop 4.4 and supports python 2.7. For KDevelop 4.5 he is already busily hacking away on kdev-python 1.5 which should then finally support Python 3.
[image: first of , title: Python Language Support]
On the ruby front we also saw lots of improvement thanks to the hard work of Miquel and Alexander. Building on top of Miquel's work  during GSOC this year, they improved the Ruby plugin until it managed to successfully parse Alexanders large Ruby on Rails source projects.  While this work required lots of changes to the language plugin, they also worked on proper Ruby support for the new File Templates and Unit Testing features for KDevelop .
[image: Any of , title: Ruby Language Support]
: http://www.mssola.com/2012/08/gsoc-improving-kdevelop-ruby-support.html : http://adymo.blogspot.de/2012/10/katekdevelop-sprint-new-ruby-language.html : http://adymo.blogspot.de/2012/10/katekdevelop-sprint-more-progress-with.html
[image: any from ]
Besides working on shiny new language support plugins, our existing C++ language support was continuously improved as well during the sprint. Sven fixed a few annoying bugs in C++ code completion, while Olivier worked on a new "lookahead matching" code completion feature (see screenshot). He landed it in master shortly after the sprint and awaits feedback from our daring users: Is it useful? Is it fast enough? Can it be better? How to reduce noise?
Olivier also worked very hard on improving the template support in our C++ language support. He introduced a new template resolver which finally chooses the correct specializations in most places. He also managed to remove many useless instantiations (up to 75% in some cases) which results in smaller DUChain caches and faster performance in general.
While it is sad, it is still a reality: Quanta is dead since we do not have enough man power. The bright side is that KDevelop is already a very good - in many parts even much superior - alternative to the Quanta you may know and love from KDE 3 times. Especially the excellent language support for PHP, Ruby and Python makes KDevelop users much more productive when writing code for the web. Still, people miss some of the neat little functionalities of Quanta.
There existed a so-called Quanta 4 port which was basically just an IDE on top of KDevplatform (just like KDevelop) with some additional web development plugins. But there was never a proper release of these already quite functional plugins. Thus Niko finally took some time during the sprint to create separate repositories for the plugins that used to live inside the Quanta repository . Afterwards he ensured that the plugins work properly with a recent KDevelop version and created a first release for the SQL plugin , the XDebug PHP Debugger  and last but not least the Upload plugin . There is also a quite nice CSS language support plugin. The other plugins are not in a good shape and will need some work, such as the XML/HTML language support, Crossfire debugger integration and a PHP source formatter plugin.
Anyhow, expect to see new stable releases of many of those plugins in the future, together with the KDevelop 4.5 release.
: http://nikosams.blogspot.de/2012/11/quanta-update.html : http://nikosams.blogspot.de/2012/10/execute-sql-kdevelop-plugin.html : http://nikosams.blogspot.de/2012/10/kdevelop-xdebug-php-debugger-beta.html : http://nikosams.blogspot.de/2012/11/kdevelop-upload-plugin-like-quanta- had.html
We did not only spent time on new features though. Face to face discussion and pair programming enabled us to improve and polish many parts of our user interface. This is always a huge advantage of such hack sprints and just shows how important it is to regularly meet in person.
So what has changed? Sven and Aleix spent some time on beautifying our settings dialog  which meant adding nice icons here and there as well as restructuring the form layouts a bit.
[image: from  title: Beautified Configuration Dialog]
Furthermore they once again worked on improving our launch configuration dialog . Here they tried to simplify it as much as possible, to make it simpler for new comers to create custom launch configurations. The simpler UI is also much more visually appealing thanks to the reduced cruft and clutter.
[image: bottom of  title: Polished Launch Configuration Dialog]
Besides such visual polish, the KDevelop source base saw lots of other smaller improvements over the week of the sprint. Milian further optimized the Quick Open feature for large projects with thousands of files. Furthermore he ensured that the results of the "Show Uses" action are now always shown in a toolview and never in a tooltip which could accidentally be closed. The "Open with" plugin also saw many improvements .
[image: bottom of  title: Improved Open With]
Aleix was busy further improving the CMake support in KDevelop. He also polished the Welcome Page which was added in KDevelop 4.4 , improved our "Pick Session" dialog and created a new Plasmoid launcher. Together with Milian he also created a new assistant which automatically renames a file if it contains a class which was renamed, i.e.: You have a class Foo in Foo.h and Foo.cpp and rename the class Foo to Bar. Now KDevelop offers you to automatically rename the files Foo.h and Foo.cpp to Bar.h and Bar.cpp respectively.
Niko spent some time on polishing and fixing bugs in the generic manager and our file system view . He added a drag'n'drop context menu to our project menu, just as you know it from Dolphin and KMail for example. The file system now supports bookmarks thanks to him. Furthermore, he improved our Git integration and fixed some bugs in the GDB debugger support.
[image: first from , title: Drag'n'Drop Context Menu]
Finally, and this might be important for packagers, Olivier changed the location of our DUChain cache, from `~/.kdevduchain` to `$XDG_CACHE_HOME/kdevduchain`, which by default is `~/.cache/kdevduchain` but often remapped to some other location if your home directory lives on a network share. You can now also set a custom location using the new `$KDEV_DUCHAIN_DIR` environment variable if you wish to do so. Note: The old cache directory is not removed automatically, thus if you run KDevelop master, or KDevelop 4.5 in the future, make sure to remove `~/.kdevduchain`.