All posts by Christoph Cullmann

Dr.-Ing. Christoph Cullmann is a Senior Software Engineer at AbsInt Angewandte Informatik GmbH. His work is focused on static analysis of both binary and source programs and the WCET analysis of embedded systems. In his spare time, he works on the KDE project and maintains the Kate editor application and component.

Kate/KDevelop Sprint 2015 – Summary for Kate

The end of the joint Kate/KDevelop Sprint 2015 is coming closer, half of the people already have left to get home.

It was a good thing to have this sprint sponsored by the KDE e.V. and organized by Milian Wolff directly after the Qt World Summit 2015 here in Berlin. I think that made it easier for people to attend both events, like myself ;=)

I came to the sprint to work on getting our bugs sorted and fixed and to improve the state of the Mac port. I must confess, the bug fixing session worked out well, but I didn’t take a shot at Mac at all.

What did I achieve? I fixed many small bugs and I reintroduced the automatic brackets completion removed by accident in the KDE 4.x => KF5 transition.

In addition I cleaned up old things in our bugzilla. The new policy for Kate will be: wishes that not got any attention since 2 years will be closed, it makes no sense to keep them around for ever and it will only make overview about what is really wanted impossible.

In addition, I tried to help Kåre Särs to get Kate running on Windows. We want to have a way to build Kate with a unpatched Qt. At the moment that is not really feasible, as things like ui files are not found, xml syntax files are not found and so on. I started to solve that issues and at least KTextEditor framework itself should now be more or less Windows (and therefore Mac) compatible. But the other frameworks will still need love, like KXmlGui not being able to locate its own ui_standards.rc. Kate application is now compilable without any strange patches, too, on Windows.

Mandatory screenshot (be aware, to get menus and stuff working, we here randomly copied all files into the right user local directories):

Kate on Windows

Dominik Haumann did help us in our bug fixing effort, too. At the end of the sprint he started the painful work to review and fix the use of hard-coded colors in our highlighting files, work nobody really wants to do :=)

Sven Brauch helped to improve my reintroduced bracket completion to be not completely dumb .P

All in all, I think it was a productive sprint. Not that we all reached our goals, but we did make progress.

I think Kate & KTextEditor will be in a very good shape for the 15.16 KF5 Frameworks  and the next KDE Applications release. In addition you always get again momentum to work on more stuff in the close future by meeting up in person and do some socializing aka eating 😉

Therefore, to wrap it up: Nice work all guys, thanks by the Kate maintainer to all people that joint the sprint and special thanks to Milian for setting it up and the KDE e.V. for sponsoring it ;=)

P.S. Yeah, sponsoring implies that the e.V. has money for that. To keep such spring sponsoring possible in the future => give us money!

Qt World Summit + Kate/KDevelop Sprint in Berlin

This week is really busy, first three days of Qt World Summit and now hacking away at the Kate/KDevelop sprint in Berlin.

This year my personal goal will be to get our bugs & wishes back into shape.

One major decision I as the maintainer did take was to close all wishes that not got changed since two years. Our team is very small and we have plenty of real bugs to take care of (and their number is rising) such that we will never be able to implement random requests.

If an user is really interested in the feature to come into existance, the wish can be reopened. Still, if no new arguments are brought up that might lead to some more interest by the Kate team, I think that won’t help a lot. The best solution would be if people could provide patches, which in some cases, like for missing highlighting features in the syntax files, is really easy. At least it should be for the advanced user crowd attracted by an advanced text editor.

Akademy 2015 & Kate

Today, I will travel back home from Akademy 2015.

I must say, it was really a nice KDE meeting and I had a lot of fun ;=)
The first day the KDE e.V. general assembly did take place, then two days of actually interesting talks (including the great announcement of Plasma Mobile). After some more days with interesting BoFs and hacking, Akademy is now ending for me.

I didn’t do that much work on Kate, I mostly did small bugfixes for the applications bundled with the KDE Applications releases regarding their HiDPI support, finally no Konsole that can’t redraw correctly on scrolling on a HiDPI screen with scaling activated!

For Kate, the most stuff I did was porting one more plugin (the text filter plugin), fixing some small bugs and rearranging the search bars for in document and in files search. I hope it now is a bit nicer to use, still that is not the final state and I guess we will ask the VDG for more input later on. (btw., if you see any HiDPI glitches in Kate/KTextEditor master, please inform me, I really want to have non-pixelated output ;=)

A big thanks to all organizers & helpers of Akademy 2015! You did a great job, it was a lot of fun, the location was nice, the social event + day trip was good, all fine 🙂 One of the nicer Akademy experiences! Lets hope that the flight home works out, as Dominik is taking the same plane, otherwise the Kate workforce will be seriously diminished.

KDE Applications Versioning

A common problem for many applications contained in the KDE Applications releases are non-incremented version numbers. Often the maintainer forgets to update the version number of the application, like I did it for Kate since the first KF5 based release.

This means: On Bugzilla, I get bugreports that always tell me “Kate 5.0.0”, not very helpful.

KDE Frameworks solves this by automatic setting of the current framework release version in all framework CMakeLists.txt.

For KDE Applications, we have now optional the same concept. For details: visit https://community.kde.org/Applications/Versioning

In short: If you are to lazy to update your version number yourself or are just fine with using the same version number als the KDE Applications releases, you can add the following three lines to your toplevel CMakeLists.txt:

# KDE Application Version, managed by release script
set (KDE_APPLICATIONS_VERSION_MAJOR "15")
set (KDE_APPLICATIONS_VERSION_MINOR "04")
set (KDE_APPLICATIONS_VERSION_MICRO "0")

These variables will then be patched by the release scripts to the “right” version for the current release series.
You can than either just use the MICRO version to suffix your own applications version to differentiate the bugfix releases or like Kate construct your complete version number from the three vars and be done ;=)

I hope this helps to have more consistent and more important meaningful version numbers once again in the applications we bundle. Thanks to all people that made this “magic” happen ;=)