KDevelop

This blog entry is a supplemental to the KDevelop 4.0 release announcement to show off the new stable release with some nice screenshots. So enjoy 🙂 KDevelop after starting and opening a project and file Quick Outline of the current file PHP Quick Outline Quick Open in PHP project As-You-Type Code Completion More Verbose manual […]

This blog entry is a supplemental to the KDevelop 4.0 release announcement to show off the new stable release with some nice screenshots. So enjoy KDevelop after starting and opening a project and file Quick Outline of the current file PHP Quick Outline Quick Open in PHP project As-You-Type Code Completion More Verbose manual Code [...]

This blog entry is a supplemental to the KDevelop 4.0 release announcement to show off the new stable release with some nice screenshots. So enjoy🙂 KDevelop after starting and opening a project and file Quick Outline of the current file PHP Quick Outline Quick Open in PHP project As-You-Type Code Completion More Verbose manual Code […]

This blog entry is a supplemental to the KDevelop 4.0 release announcement to show off the new stable release with some nice screenshots. So enjoy KDevelop after starting and opening a project and file Quick Outline of the current file PHP Quick Outline Quick Open in PHP project As-You-Type Code Completion More Verbose manual Code […]

This blog entry is a supplemental to the KDevelop 4.0 release announcement to show off the new stable release with some nice screenshots. So enjoy 🙂 KDevelop after starting and opening a project and file Quick Outline of the current file PHP Quick Outline Quick Open in PHP project As-You-Type Code Completion More Verbose manual […]

This time around svn got me, I’ve used the createtarball script from kdesdk to generate the RC2 tarballs so we ship translations. This worked just fine, except that for some unknown reason svn likes to not check out svn:externals when doing an svn co of kdevplatform. This resulted in a kdevplatform tarball (yes I didn’t test-compile [...]

This time around svn got me, I’ve used the createtarball script from kdesdk to generate the RC2 tarballs so we ship translations. This worked just fine, except that for some unknown reason svn likes to not check out svn:externals when doing an svn co of kdevplatform. This resulted in a kdevplatform tarball (yes I didn’t […]

This time around svn got me, I’ve used the createtarball script from kdesdk to generate the RC2 tarballs so we ship translations. This worked just fine, except that for some unknown reason svn likes to not check out svn:externals when doing an svn co of kdevplatform. This resulted in a kdevplatform tarball (yes I didn’t […]

Finally getting around to blog about this. We’ve released RC1 of KDevelop4 today. We’ve fixed a couple of bugs and got some good performance improvements, but even more will be in RC2. RC2 will also ship with translations, for RC1 we’ve discovered a severe problem that we couldn’t fix anymore in time related to translations. On behalf [...]

Ok, you should know by now that I love profiling and making things faster. Yet there’s always a “but”. For me it’s blocking syscalls, or anything that makes the app “slow” for the user but doesn’t show up in Callgrind as the Instruction Fetch cost ... [More] doesn’t go up. The usual suspect is of course locks (which we have quite a lot in KDevelop) or QProcesses with waitForFinished() or similar… You won’t see them in any Callgrind profile. Does anyone know a way to achieve that? Something that makes Callgrind increase the Ir cost for blocking func calls depending on the time it blocks? Or some other tool that would show me these? And if you are interested: I was still able to find the cause for slow parsing of Custom Make Manager projects (Qt, Linux Kernel, …) in KDevelop: The cache in the IncludePathResolver never hit, since a operator== was improperly implemented ;-) I really wonder how we could have missed that for so long! I’ve also added some more changes that should make it much faster to parse projects that rely on the IncludePathResolver. I was personally now able to parse 10.000 files of the Linux Kernel in about 9.5 minutes. This is roughly a third of the Kernel, so I’d get to a total of approx 30min. Compare that to the 2.5h for 5% that one of our users reported ;-) [Less]