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…
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’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: http://kde-apps.org/content/show.php?content=122409
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: https://trac.macports.org/ticket/27168
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).
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:
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 git.kde.org 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.
I’m happy to announce the immediate availability of KDevelop 4.1 RC 1. This is a testing release, and any feedback is greatly appreciated. Please send us your feedback either via one of our mailing lists,
#kdevelop on freenode or put general bugs and wish request as always to http://bugs.kde.org. We are quite confident that this release is ready for every-day use, and if nothing unplanned happens, we are going to release KDevelop 4.1 in about two weeks.
MD5 Sum: `c652788d44ec4b4b09bc2d26f2ae2068`
SHA1 Sum: `e6a87146f69c4149ee669de21dc171020285f17a` KDevelop 4.0.90
MD5 Sum: `2d0028a60a0beecb0e3f6e442f2e7be3`
SHA1 Sum: `72bb75a5dcf3e23165cfc5e00d92229012752fd3` KDevelop PHP 1.0.90
Hello dear lazyweb,
I have a problem that I could not solve nor find help by my usual paths. I’m speaking about a deadlock on shutdown I get sometimes with what will become KDevelop 4.1. You can find a backtrace in this bug report:
The thing is this: Apparently some global
QMutex is getting destroyed by the exit handler but the call to
__pthread_cond_destroy does not return.
I have no clue on how to fix this. Is there at least a way to find out which mutex this is? Someone told me to have a look in
/proc/PID/maps but there I only found out that - what a suprise -
~QMutex is defined in
libQtCore.so… Or should I have looked for the
this=0xfffffe00 address? Speaking of which - isn’t that address messed up?
Does anyone have a better idea?
Good news everyone!
I’m happy to announce the immediate availability of KDevelop 4.1 Beta 3. This is a testing release, any feedback is greatly appreciated. But keep in mind that it might exhibit unexpected behavior and eat your children. Please send us your feedback either via one of our mailing lists,
#kdevelop on freenode or put general bugs and wish request as always to http://bugs.kde.org.
MD5 Sum: `2adf7d05558d9c0dd1e4e98ccf67b423`
SHA1 Sum: `940a326bdd300fc435e8699d392fb85c6945dc91` KDevelop 4.0.82
MD5 Sum: `192e8ba827bfebd090740b138418f4c6`
SHA1 Sum: `f9ea5ea9b9f07c338426a1f5d42584090bbb590b` KDevelop PHP 1.0.82
MD5 Sum: `e25c351d62e70931f0466c831fa16c6f`
SHA1 Sum: `f9ea5ea9b9f07c338426a1f5d42584090bbb590b` KDevelop PHP Docs 1.0.82
Good news everyone, this time in a double feature!
I’m happy to announce the availability of two new additions to the KDevelop release family:
KDevelop 4.0.2 stable release
Lets begin with the boring part: We have released KDevelop 4.0.2, together with KDevplatform and the PHP plugins. You can find the sources here:
This is a bugfix only release and everyone is urged to upgrade as soon as possible. Users should wait for their distributions to provide packages for them. The tarballs contain changelogs if you are interested what happened since 4.0.1. Or read them online:
I was on a spontaneous trip last week and missed the Beta 2 release. Apol took over but my instructions where not clear enough and the packages where totally screwed up (the tags pointed to code in master, no the 4.1 branch).
I’m in the process of fixing things up and will create tarballs for Beta 3 and announce it to packagers later today.
Lets hope the actual release for users out there can happen later this week.
Sorry again, bye.
Hello everyone, the “I can syntax highlight everything” guy speaking again :)
Yeah, I couldn’t sleep well after I put colors on Dr Konqi. I also did the same for Kate, if you did not notice it. There is a new GDB Backtrace syntax highlighting file for it, giving you the same pleasant experience you are now used to from Dr Konqi. Awesome.
But well, lets admit it: What use are these two for bug triaging? Visit any crash report on bko and you are left to plain old black-on-white… Stone-age stuff, lets put it on LSD, shall we not? I propose: The GDB Backtrace highlighter GreaseMonkey userscript!
Download User Script (Requires GreaseMonkey 0.8 or higher)
Bug reports, feedback, pizza & beer all welcome :)