Blog Syndicate content

  • » KDevelop 4.2 Beta 1 released

    Fri, 12/17/2010 - 22:49

    Hey all,

    I’m happy to announce the immediate availability of KDevelop 4.2 Beta 1. This is a testing version and any kind of feedback would be welcome and appreciated. Please use our bugtracker. You can download the sources or wait for your distribution to create packages.

    Note: Anyone who runs KDE 4.6 or later needs this version (or any later). This is because the SmartRange interface in Kate got nuked and replaced with MovingRange interface. Many thanks to David Nolden for more or less single handedly porting KDevelop to this new architecture.

    The good news doesn’t end here though, KDevelop 4.2 ships with lots of notable changes and new features:

    • MovingRange` support (Thanks to David Nolden)
    • Grep Plugin rewrite with replace functionality (Thanks to Silvere Lestang, Julien Desgats, Benjamin Port)
    • QtHelp plugin now supports arbitrary .qch files (Thanks to Benjamin Port)
    • ManPage plugin (Thanks to Benjamin Port, Yannick Motta)
    • new look for code assistants (Thanks to Olivier JG)
    • filter for the project model view (Thanks to Eugene Agafonov)
    • improved “Problems” toolview, along with “TODO/FIXME” browsing (Thanks to Dmitry Risenberg)
    • better standards compliance in the C++ macro implementation (Thanks to Dmitry Risenberg)
    • argument dependent lookup for the C++ plugin (Thanks to Ciprian Ciubotariu)
    • open with external application by default (esp. useful for Qt Designer .ui files)
    • PHP: rainbow colors for all vars (and no nested functions or similar), esp. useful for scripts without Classes/Functions
    • code cleanup for working sets
    • better handling of locked sessions (locked session gets activated or the user gets asked whether he wants to remove the lock file)
    • improved Snippets editing usability

    Along with these big changes, lots of small improvements have been made and we will continue to polish and harden out this branch in order to give you a stable, fast KDevelop 4.2 soon. Considering the impact and amount of changes, testing would be very welcome in order to prevent regressions and similar in the final 4.2 version.

    Bye and thanks again to all contributors who made this possible. I’m especially thrilled to welcome so many new people, well done!

  • » Third Google CodeIn Screencast - Snippets

    Sun, 12/12/2010 - 19:20

    Hey everyone,

    the third screencast for KDevelop is in:

    It shows the advanced snippets support in KDevelop, see also: Snippets in KDevelop & Kate.

    In an unrelated note: I’ll do a talk at the Computer Science faculty of the FU Berlin tomorrow, see:

    13.12.2010, 18 Uhr, Hörsaal der Informatik

    “Wie und warum man sich als Open Source Entwickler/in engagieren sollte”

    Viele Studenten könnten gute Programmierer sein, aber lassen Ihr Talent ungenutzt oder stecken es in private (kleinst) Projekte und One-Man-Vaporware. Würden sie sich hingegen in bestehenden Open Source Projekten engagieren, würde ihr Lieblingsprojekt nicht nur ein Stück besser werden, sondern sie selbst gewännen dabei eine Menge. Was ein paar dieser Vorteile sind, und wie man überhaupt damit anfängt sich in einem großen Projekt zu beteiligen, möchte ich am Beispiel von KDE zeigen und hoffe, dass dadurch ein paar mehr von euch aktiv in einem FOSS Projekt mitarbeiten werden.

    Anyone is invited to attend of course :)


  • » Should all callgrind bottlenecks be optimized?

    Thu, 12/09/2010 - 19:12

    Hey all,

    I’d like to have some feedback from you. Consider this code:

    1. #include <iostream>
    2. #include <memory.h>
    4. using namespace std;
    6. struct List {
    7. List(int size) {
    8. begin = new int[size];
    9. memset(begin, 0, size);
    10. end = begin + size;
    11. }
    12. ~List() {
    13. delete[] begin;
    14. }
    15. int at(int i) const {
    16. return begin[i];
    17. }
    18. int size() const {
    19. // std::cout << "size called" << std::endl;
    20. return end - begin;
    21. }
    22. int& operator[](int i) {
    23. return begin[i];
    24. }
    26. private:
    27. int* begin;
    28. int* end;
    29. };
    31. int main() {
    32. const int s = 1000000;
    33. for (int reps = 0; reps < 1000; ++reps) {
    34. List l(s);
    35. List l2(s);
    36. // version 1
    37. for ( int i = 0; i < l.size(); ++i ) {
    38. // version 2
    39. // for ( int i = 0, c = l.size(); i < c; ++i ) {
    40. l2[i] =;;
    41. }
    42. }
    43. return 0;
    44. }

    If you run this through callgrind, you’ll see quite some time being spent in l.size(), the compiler doesn’t seem to optimize that away. Now, fixing this “bottleneck” is simple, look at version 2. That way, l.size() will only be called once and you’ll save quite some instructions according to callgrind.

    Now, my first impression was: Yes, lets fix this! On the other hand, this optimization is not really that noticable in terms of user-experience. So my question is: Is it worth it? Should everything one sees in callgrind that is easily avoidable and optimizable (like the stuff above) be optimized?

    I ask because QTextEngine e.g. doesn’t use the optimized version and I wonder whether I should create a merge request for that. According to callgrind the difference is noticeable: One of my testcases shows ~8% of the time being spent in QVector<QScriptItem>::size() (via QTextEngine::setBoundary()). In Kate the difference is even bigger with ~16% of the time being spent in QList<QTextLayout:.FormatRange>::size() via QTextEngine::format(). Hence I’d say: yes, lets optimize that. I just wonder whether it’s noticeably in the end.


    EDIT: See this comment thread for an answer.

  • » Second Google CodeIn Screencast: Advanced C++ Support in KDevelop 4

    Tue, 12/07/2010 - 18:29

    Hey all,

    just a quick note: The second google code-in task for KDevelop got completed, this time by Furkan Üzümcü. He shows off some features in KDevelop 4 that together make up the advanced C++ support you can find in it. Take a look at it:

    Thanks to Furkan and Google for doing this.

  • » KDevelop 4.1.1 released

    Mon, 11/29/2010 - 00:26

    Good news everyone!

    I’m happy to announce the immediate availability of KDevelop 4.1.1, a pure bug fix release. Every user is urged to upgrade to this new and improved version.

    You can download the sources from one of the mirros. Though most users should get this update via a distribution package update.

    Changelog for KDevelop 4.1.1
    1. ChangeLog for kdevplatform v1.1.1
    2. =================================
    4. * Milian Wolff: set version to 1.1.1
    5. * Aleix Pol: Make the build tool responsible for renaming the items when rename is triggered (it was already being done, but twice in abstractfilemanagerplugin).
    6. * Dmitry Risenberg: Fix line numbers in annotation bar for git. BUG:255599
    7. * Pino Toscano: i18n: do not extract messages from sources in 'tests' subdirectories
    8. * Nicolás Alvarez: Minor changes to apidox.
    9. * Aleix Pol: When removing a file or directory, check if it has git versioned stuff. In that case ask Git to remove it, otherwise trash it.
    10. * Nicolás Alvarez: Fix comment typos in iplugin.h.
    11. * ben2367: Correct FileManager contextMenu
    12. * Nicolás Alvarez: Add i18n comments to strings in codeutils plugin.
    13. * Nicolás Alvarez: DumpChain: code cleanup.
    14. * Milian Wolff: fix: don't crash when changing shortcuts without having an active document
    15. * Milian Wolff: set a proper minimum width when initializing the launch config dialog
    16. * Milian Wolff: make sure all projects are readable in launch config dialog
    17. * Milian Wolff: initialize CodeHighlightingColors after we initialized the required member vars, add test to run valgrind easily
    18. * Lambert CLARA: Fix lib APU find in FindSubversionLibrary.cmake
    19. * Milian Wolff: preserve remote parts of url of active document for 'open file' dialog
    20. * Aleix Pol: Copy the current directory instead of doing silly references.
    21. * Milian Wolff: add some icons in the launch config dialog
    22. * Milian Wolff: fix resize-to-column width algorithm and make launch config dialog have a sane size by default
    23. * Milian Wolff: disable target combobox when using custom executable
    24. * Milian Wolff: try to fix crash in KDevelop::ConfigurableHighlightingColors::getAttribute
    25. * Milian Wolff: fix up delegate deletion, prevents crash in generic manager test cases (was deleted but the static var in the getter function was not reset)
    26. * Milian Wolff: backport from master: only append subdirs to actual parent list jobs, fixes random crashes
    27. * Nicolás Alvarez: Add 'build' to .gitignore.
    28. * Milian Wolff: make project url canonical before inserting into m_currentlyOpening
    29. * Milian Wolff: don't leak temporary files
    1. ChangeLog for kdevelop v4.1.1
    2. =============================
    4. * Milian Wolff: set version to 4.1.1
    5. * Pino Toscano: i18n: do not extract messages from sources in 'tests' subdirectories
    6. * Burkhard Lück: fix wrong usage of translation context in ui file messages to make the translated strings visible either use <string comment="bar">foo</string> or <string extracomment="@info">foo</string>
    7. * Milian Wolff: backport from master: when using parallel builds, make install with kdesudo uses a command string like: kdesudo -t -c make -j4 install
    8. * Nicolás Alvarez: Cleanup and typo fixes in code comments.
    9. * Nicolás Alvarez: Use qSwap instead of custom "tmp=a; a=b; b=tmp;" code.
    10. * Milian Wolff: fix: make sure we compare directores without slashes as KDevelop API's urls have slashes while QDir::entryInfoList will never have slashes
    11. * Aleix Pol: Provide support for break in foreach command.
    12. * Aleix Pol: comment for performance issues.
    13. * Aleix Pol: Added support for CMAKE_CURRENT_LIST_DIR variable.
    14. * Aleix Pol: When looking for cmake modules, look for the directories without lowercases. It should work too.
    15. * Milian Wolff: don't try to get namespace for dot and dotdot, prevents pesty warning:
    16. * Milian Wolff: fix: prevent crash, don't try to access duchainpointer blindly
    17. * Milian Wolff: fix: unbreak 'Force Tabs' in astyle formatter settings
    18. * Milian Wolff: fix: make sure to apply negative BlockBreakAll option
    19. * Milian Wolff: never switch to the implementation of a signal (i.e. the .moc file), instead use fallback and switch to .cpp
    20. * Milian Wolff: backport from master: disable DEBUG_UI_LOCKUP by default, if desired enabled it via cmake (BUILD_uiblocktester option)
    1. ChangeLog for php v1.1.1
    2. ========================
    4. * Milian Wolff: set version to 1.1.1
    5. * Milian Wolff: fix: remove obsolete mention of application/x-gzip in supported mimetype list

    Additional to these changes, the translations have been improved and updated.

    As always, many thanks to all the contributors who made this possible.

  • » Google Code In: First KDevelop Documentation Screencast!

    Sat, 11/27/2010 - 19:21

    Woha, back when Lydia announced Google Code In and asked me whether I’d like to mentor some KDevelop projects, I wasn’t so sure this was a good thing. But then I saw that documentation could be requested from the students, and well… KDevelop 4 has no real documentation (except this) - why shouldn’t I try it?

    So I put a few “screencast workflow XYZ” tasks into Google’s Melange Web Interface (which btw. sucks so much it’s incredible) and forgot about it. I didn’t really think there would be school students being interested in KDevelop, esp. not in writing documentation or doing a screencast. But thankfully I was proven wrong, and in all levels. Please behold, the first documentation screencast for KDevelop, showing you how to get started with a project, setting up a launch configuration, and doing some basic debugging:

    I’m amazed by the quality of that video, very well done Geoffry and thanks already to Google for the Code In. Lets hope more students will provide me with such good work :) And I hope this helps some users to get started with KDevelop 4.

    PS: KDevelop 4.1.1 will be anounced tomorrow, replace functionality was merged for the “Find in Files” plugin and development is actively continuing :)

    PPS: We still want to improve the launch configuration dialog :D

  • » Quanta compiles against KDevelop master again!

    Sun, 11/21/2010 - 20:57

    Hey all,

    another blog post today, I’m on fire :) This one is shorter though: I want to notify you all that Quanta compiles against KDevelop master again (i.e. what will become 4.2 and uses the MovingInterface from Kate).

    If you are using KDevelop 4.1 and want to use one of the Quanta plugins, like XML or CSS language support or XDebug or Crossfire integration, checkout the 4.1 branch.

    I hope to work more on Quanta again over the next days, hope I can finally get it into a usable state…


  • » KDevelop and Kate advancements over the last weeks

    Sun, 11/21/2010 - 17:38

    Hey all,

    I didn’t blog in a long while so I thought I’d dump some notable things I did over the last weeks. It’s probably neither complete nor thorough - you should try it all out to see it for yourself :)


    Lets start small with my Kate contributions. I really concentrate on KDevelop nowadays since Kate works quite well for me and I don’t have many itches to scratch anymore :) So, what did I do these last weeks? Mostly cleanup and performance work, especially regarding MovingRanges which of course is mostly needed for a good experience in the upcoming KDevelop 4.2. With the help of Dominik Haumann I also went through our indentation unit tests and made sure we expect all currently failing test cases, as well as fixing those I could. Now we (finally!) have a passing test suite and get noticed about introduced regressions. Awesome!


    Of course I still concentrate my contributions on KDevelop and related plugins. What I find quite interesting is that I’m now for over two months in a “polish-and-bugfixing”-mode, without adding much new features. I think that shows that I’m quite satisfied with the existing features, just not with the way they are integrated. E.g. the Kate performance improvements above were done in order to make “reformat source” not hang the IDE for a couple of seconds anymore, in KDevelop 4.2 it will only be like one second for really big source files. I’ve also tackled our black sheep, the “launch configuration” dialog. I didn’t rewrite it, but I did some polishing and have some more ideas to hopefully get it into a useable state. Oh, I just remember: I also spent some time on the “Snippets” plugin, restructured the editor dialogs a bit and made them use Katepart as well, for syntax highlighting and proper editor features :)

    I generally care about small things nowadays, like e.g. that all widgets have a proper tooltip. This is also something where you all could help: If you find a widget in KDevelop master (4.2) that has no tooltip, please notify me! I’ve added those e.g. to the outline and quickopen toolbar widgets among others.

    And since KDevelop 4.1 was in beta stage I’ve fixed lots of bugs and continue to do that. I triage each new bug for KDevelop/KDevplatform, request feedback and valgrind logs and try to fix whatever I can. Even now I can safely assume that KDevelop 4.2 will be more stable than 4.1, even though we did lots of architectural changes in the platform, esp. regarding MovingRanges.

    And now to the last and to me most pleasing part: New features! Remember how I said I didn’t do lots of feature development at all these past days? This is basically true, instead I let others do the work :) We really get more and more patches and merge requests by other people, and I did merge quite some changes already. We have an improved “find in files” plugin now, and the French students are working hard on giving it replace functionality as well! We already merged their improved QtHelp plugin that gives you the ability to integrate arbitrary .qch files into KDevelop, e.g. the KDE Api documentation. They also work on [man integration](, which will be a joy for all STD C / C++ developers.

    Furthermore we now have a “Filter…” line edit above the project manager view, “Argument Dependent Lookup” for the C++ plugin, a much improved “Problems” toolview, with the ability to show TODOs etc. pp.

    This is just from the last few weeks, and it’s work done by many new contributors. It’s really very cool to see this happening.

    Oh, and I personally worked a bit on the QMake support for KDevelop, I’m not sure whether I will manage to get this into a usable state for KDevelop 4.2, but I already use it at work.

    Which brings me to the last part of this blog post, release schedules! I’ll finally release a KDevelop 4.1.1 bug fix version next week, and will make sure that there is a 4.2 release just before / shortly after the KDE 4.6 release in January. The big “issue” there is that KDevelop 4.1 will not work with KDE 4.6+, since there are no SmartRanges in Kate from 4.6 anymore. So a big fat warning to any adventurous tester out there: If you want to try KDE 4.6 betas, remember that you’ll have to get KDevelop master (== 4.2) as well somehow!

    So, that’s it for now, have a nice sunday everyone :)

  • » Massif Visualizer 0.2 released

    Sun, 11/07/2010 - 00:16

    Hey all!

    I’m happy to release Massif Visualizer v0.2. This is mainly a “fix the build-system” release, no new features have been added.

    You can download it here:

    Mac Support

    Thanks to the reports by Chris Jones it’s now possible to build and use Massif Visualizer on Max OS X, see e.g.:

    He has also submitted the portsfile for inclusion in Macports:

    KGraphViewer now optional

    I’ve made the KGraphViewer dependency optional, if anyone does not want it (even though this removes like 50% of the tools features).

    KDE Infrastructure

    I’ve also prepared the steps for moving Massif-Visualizer into KDE Extragear and asked kde-devel for review. I already use the KDE infrastructure now:

    git clone git://
    Bug tracker:
    Mailing List:

    This also means that I’ll shortly get translations by the awesome KDE-i18n-Team, so stay tuned for a 0.3 including translations!

    Open Suse Buildservice

    I’ve also spent quite some time today battling with OBS and can provide at least packages for Fedora, Mandriva and Open Suse now. I’m still waiting for help on the remaining issues and once they are resolved I’ll add the remaining packages.

    1. ChangeLog for massif-visualizer v0.2
    2. ====================================
    4. * Milian Wolff: set version to 0.2
    5. * Milian Wolff: fix conditional
    6. * Milian Wolff: make kgraphviewer dependency optional
    7. * Milian Wolff: fix FindKGraphViewer.cmake
    8. * Milian Wolff: fix .po name
    9. * Milian Wolff: remove some esoteric cli option for XGETTEXT that does not make
    10. any sense according to Albert
    11. * Milian Wolff: fix: install libs to make sure they can get loaded on OSX e.g.
    12. * Milian Wolff: fix compile warning about init order, improve style by having
    13. just one init per line
    14. * Milian Wolff: add export macros everywhere, make visualizer helper use the
    15. Massif namespace as well
    16. * Milian Wolff: add
  • » Massif Visualizer 0.1 released

    Tue, 11/02/2010 - 19:06

    Good news everyone!

    Since Gaël finally came around to release KGraphViewer 2.1, I can go ahead and do the same for Massif Visualizer!

    Download Massif Visualizer 0.1

    This is the first release and I would be very happy if more users gave me their feedback. I intend to move to soon in order to leverage the KDE infrastructure (mostly translations, bug tracker, releases)… This also means: There are no translations yet! I also intend to update my OBS repository to provide packages for the first release.

    Stay tuned for updates.