Posts 

NOTE: Please refer to Get It for up-to-date Windows versions It took some time but here is now an installer for Kate on Windows. First the proof :) [][2]The installer [][3]An example of what it can look like There are still some things that needs fixing. The current installer is built from git master and not from released packages so the translation stuff hat you usually get with the release packages are missing. So only partially translated. Another feature that I’m still missing is the spell-check. I need to still add a/hspell and language dictionaries to get that to work. Read More

After a bit more work, toolbars (and other places ;=) have icons, too. More Kate plugins do work, like the nice project plugin I use the whole day, see: Updated .dmg files can be found at (alpha quality, only tested on Mac OS 10.10): ftp://kate-editor.org/cullmann/kate-20151024.dmg Read More

Hi, with my latest changes in kate.git, icons work, too, on windows and mac, without any qt patch, if you put some qt resource file containing breeze inside your share or Resources folder (one up from the application binary). mac.txt contains the rcc calls needed to create such a package and all others things you need to run to get .dmg files. (you need Qt 5.5.0 + a recent CMake + XCode with command line stuff enabled) Read More

Hi, after one week of patching frameworks (and KWrite/Kate), the first success can be seen: a kind of working application bundle for KWrite. Still no icons, need to set icon theme + search paths right and bundle that, too, but need to investigate more how the icon lookup works. Read More

Kate runs ;=) But as you can see, we have no icons, but that is as no work was invested into it and not even any icons are installed ;=) I will maintain a guide how to build it on mac in the kate.git/mac.txt file. At the moment, this is all not that nice. Kate is able to open files via file dialog and it renders OK, modulo some glitches. Read More

After some hacking on frameworks, I have the first running KWrite version on Mac that uses an unpatched Qt from the qt.io offline installer: It is still ugly, as scaled on my HiDPI display as the plist file is missing and it crashs on everything (aka open dialog) and has no icons. Read More

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. Read More

From the 7th to the 11th of October Kate and KDevelop contricutors once again met to work on both Kate and KDevelop. The work in Kate was mostly spent on fixing bugs, as can be seen by the following bug chart for Kate: That is, more than 300 bug and wish reports were closed. Granted, many of the reports were just old and given our limited manpower we were closing many wishes since it is unlikely that old wishes get implemented. Then again, we also fixed a lot of bugs that required code changes, and also fine tuning of KTextEditor and Kate. The fixed bugs are roughly KDE bug tracker (yes, the auto-brackets option is back!), besides there are also a lot of changes there were not listed in bug reports. We hope the changes are useful to you, so be sure to get the KDE Frameworks version 5.16 as soon as it’s released :-) Read More

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. Read More

To get started with KDE development, newcomers usually first sent patches. Having sent several patches, the newcomers are typically encouraged by us (the reviewers) to apply for a KDE contributor account. This application includes the question of “who encouraged you to apply for a KDE contributor account”. Then, the KDE sysadmins contact the mentioned developers to make sure the application is valid and trustworthy. Hence, you, as someone who encouraged others to apply for an account, get a mail with the subject “Developer account application approval […]”. Read More