Posts 

I reinstalled my home machine last week with openSUSE 13.2 and installed their latest 15.04 packages from the KDE repos ;=) That is the first time that I use a distro-shipped Kate that is based on KF5 (and no other Kate 4.x is installed any more as escape route). I think I already have seen 1-2 glitches (like not needed questions for reload and some repaint issue on reload), still, overall, I am happy with what is shipped as 15.04. Read More

From the KDE relicensing page: A couple of KDE dependent projects or even libraries have moved or are going to move to GPLv3. Unfortunately, GPL v3 is incompatible with GPL v2. This means that it is not possible to create a project linking GPL v2 and v3 code together. There is no problem for projects which are licensed GPLv2+ (version 2 or above). A few parts of KDE are currently licensed as GPLv2 only. So far we have no reason to believe that this was something other than an oversight. However, we still need to validate with the individual copyright holders that a relicense to GPLv2+ or GPLv2+v3 is okay with them. Read More

Look here, if you are interested.

Given that the KF5 based Kate works OK on Windows, I would like to get the Mac version up and running, too. As virtualization of MacOS X is kind of “forbidden” and not that nicely usable anyway, as no nice accelerating drivers are available for the standard vm solutions, I just went out into the world and bought some Retina MacBook. I followed the nice guide on https://github.com/haraldF/homebrew-kf5 (thanks Harald :=) and got some installed Kate/KWrite (after patching kio to skip X11 detection). Read More

For my job, I need to take care of the support of old Linux distributions for our products, therefore I experimented in building Qt 5.x for Red Hat Enterprise 5 (or CentOS 5 or other clones). Whereas Red Hat Enterprise 6 works more or less out of the box, to build Qt (even with WebKit and Co.) on Red Hat Enterprise 5, more work is needed. Even the xcb library is not yet existent there. Read More

Recently, there were some thoughts on where KDE is going, and related to that what’s the driving force behind it in terms of the pillars of KDE. Albeit it is true our development model changed significantly, I’m not convinced that it’s all about git. No, I rather believe that it is the excitement about the KDE that makes it stand out – KDE as a community if you wish, but also KDE as a software project. Read More

Here it goes, Kate5 running on Windows:This is an early version of Kate5 on Windows. It runs just fine but has some glitches, such as the white lines between selected text lines, or wrong margins in the search&replace bar, or showing a ‘+1’ in the top right corner, although all documents are visible. Read More

Since some weeks, the Kate homepage features a way to support Kate and KDE by donating money to the KDE e.V., see this screenshot: The reason for showing a donation pane might not be obvious, since the KDE project is open source and mostly developed by lots of contributors in their free time. So why do we need money? Read More

2021 Update: Kate's current mascot is Kate the Cyber Woodpecker, a refreshed version of the mascot introduced in this post. After the first KF 5 release, I contacted the creator of the Krita mascot Kiki and the KF 5 dragons artwork, Tyson Tan, if he would be interested in design a Kate mascot, too. He immediately agreed to help out and after some months of roundtrips, here we go! Kate has a mascot: Kate the Woodpecker Read More

Since KDE SC 4.10, Kate ships with the Projects plugin. This plugin provides an automatically generated structured list of files belonging to a project. Currently, in Kate 5, the Projects plugin looks like this: What’s new in the Project plugin in Kate 5 since some weeks is an auto-loading feature. In 4.x times you needed to create a .kateproject file that was then read by the Projects plugin to populate the listview. This still works in Kate 5, of course. But if a .kateproject file does not exists, you can now still read the file list from the version control system. To this end, auto-loading for the respective version control system needs to be enabled in the settings (enabled by default): Read More