Posts 

During Akademy it was brought to my (and the other Kate developers) attention, that we should take a closer look on the Binary Factory for KDE. There were some blogs about the Binary Factory in the past but we somehow never really linked it on our homepage as potential source for up-to-date installers for the different operating systems. I feel a bit sorry for neglecting that area in the past year. Therefore, as we have now some time during Akademy together as team, we did take a look at the current state of the installers there for Windows and macOS. Read More

During Akademy there was finally enough time to finalize the porting of KTextEditor to KSyntaxHighlighting. Thanks to the help of Dominik and Volker, the needed extensions to the KSyntaxHighlighting framework were done in no time ;=) Thanks for that! The branch for the integration was merged to master yesterday, unit tests look OK and I am using that state now for my normal coding work. Beside minor glitches that should now be corrected, no issues came up until now. Read More

Starting with the KDE Frameworks 5.50 release we decided to remove the capability in Kate/KTextEditor to download / update syntax highlighting files from the Kate homepage. The reasons for this are as follows: The KTextEditor framework is released once a month, meaning that users who use latest KDE software usually anyways have the most recent versions. Other users who do not follow the latest development releases (like your mom) are likely not the target audience for downloading highlighting files. There are technical problems with only updating certain highlighting files, since it can lead to an inconsistent state when one highlighting file needs another one that was not updated or does not exist, or also if a highlighting file needs a certain indenter that does not yet exist or contains bugs. We have a nice small cleanup in the UI, since we have now one button less. Git changes: Read More

After fixing some first porting bugs to KSyntaxHighlighting, code folding (non-indentation based) is back working, too. There is a still a lot to do (and e.g. the syntax colors are still kind of randomized), but already all KTextEditor original highlighting code is gone without ending up in an unusable state.

After several years, the time has come that KTextEditor finally starts to use more of KSyntaxHighlighting than just the syntax definitions resources. At the moment, we still do everything on our own (parsing the xml, doing the highlighting, …) and only use the XML files bundled inside the KSyntaxHighlighting library as “code sharing”. I started a “syntax-highlighting” branch in ktexteditor.git to change that. Dominik helped out by starting to add missing API to KSyntaxHighlighting that will ease the porting. Read More

Like Dominik, I will be around the whole Akademy, too. Looking forward to see new and old friends, lets have a productive week there!

Of course, I am going to Akademy. I’ll be there from Friday 10th to Saturday 18th. See you! :-)

When building the KSyntaxHighlighting framework, the syntax highlighting xml files are compiled into the KSyntaxHighlighting library. In order to do so, we have a small little helper program that generates an index of all xml files. This indexer also validates the xml files against the XML Schema, and performs some more sanity checks. Review request D10621 tries to extend the indexer even further and suggest optimizations for our highlighting files. For instance, the rule Read More

Just in case someone is interested: two days ago a very good article about cmake popped up, called It’s Time to do CMake Right. There also is a discussion about it on reddit/r/cpp. happy reading :)

After a long time of constant distraction by my daily work, I finally found again a bit time to take care of KTextEditor/Kate/… issues. One thing that really started to be an itch I wanted to scratch is some rendering fault that occur with ‘special’ font sizes. Given I wanted to do again a bit work on the macOS port, I was really annoyed that on my screen the only application with text rendering issues was “my” one :/ Read More