Category Archives: Developers

KSyntaxHighlighting – A new Syntax Highlighting Framework

Today, KDE Frameworks 5.28 was released with the brand new KSyntaxHighlighting framework. The announcement says:

New framework: syntax-highlighting
Syntax highlighting engine for Kate syntax definitions

This is a stand-alone implementation of the Kate syntax highlighting engine. It’s meant as a building block for text editors as well as for simple highlighted text rendering (e.g. as HTML), supporting both integration with a custom editor as well as a ready-to-use QSyntaxHighlighter sub-class.

This year, on March 31st, KDE’s advanced text editor Kate had its 15th birthday. 15 years are a long time in the software world, and during this time Kate won the hearts of many users and developers. As text editing component, Kate uses the KTextEditor framework, which is used also by applications such as KDevelop or Kile.

The KTextEditor framework essentially is an embeddable text editing component. It ships everything from painting the line numbers, the background color, the text lines with syntax highlighting, the blinking cursor to code completion and many more features. One major feature is its very powerful syntax highlighting engine, enabling us to properly highlight around 275 languages.

Each syntax highlighting is defined in terms of an xml file (many examples), as described in Kate’s documentation. These xml files are read by KTextEditor and the context based highlighting rules in these files are then used to highlight the file contents.

For the last 15 years, this syntax highlighting engine was tightly coupled with the rest of the KTextEditor code. As such, it was not possible to simply reuse the highlighting engine in other projects without using KTextEditor. This lead to the unfortunate situation, where e.g. the Qt Creator developers partly reimplemented Kate’s syntax highlighting engine in order to support other languages next to C/C++.

This changed as of today: The KSyntaxHighlighting framework is a tier 1 functional framework that solely depends on Qt (no dependency on Qt Widgets or QML), is very well unit tested, and licensed under the LGPLv2+. As mentioned in the announcement and in the API documentation, it is a stand-alone implementation of the Kate syntax highlighting engine. It’s meant as a building block for text editors as well as for simple highlighted text rendering (e.g. as HTML), supporting both integration with a custom editor as well as a ready-to-use QSyntaxHighlighter sub-class. This also implies that you can reuse this framework to add syntax highlighting to e.g. QML applications.

We hope that other applications such as Qt Creator will start to use the KSyntaxHighlighting framework, since it allows us to cleanly share one single implementation of the syntax highlighting engine.

In the next KDE Frameworks releases, we will remove KTextEditors syntax highlighting engine in favor of just using KSyntaxHighlighting. This will happen step by step. For instance, we already have a pending patch that removes all xml files from KTextEditor.git in favor of using the ones shipped by the KSyntaxHighlighting framework. That means, with the KDE Frameworks 5.29 release, Kate’s and KTextEditors dependency (and other application’s dependencies) will look as follows:

KTextEditor and KSyntaxHighlighting

This is quite an interesting change, especially since moving the syntax highlighting engine out of KTextEditor was already planned since Akademy 2013 in Bilbao:

Another idea was raised at this year’s Akademy in Bilbao: Split Kate Part’s highlighting into a separate library. This way, other applications could use the Kate Part’s highlighting system. Think of a command line tool to create highlighted html pages, or a syntax highlighter for QTextEdits. The highlighting engine right now is mostly internal to Kate Part, so such a split could happen also later after the initial release of KTextEditor on 5.

This goal is now reached – thanks to Volker Krause who did most of the work. Pretty cool!

If you are interested in using the KSyntaxHighlighting framework, feel free to contact us on our mailing list. Further, we welcome all contributions, so please send patches to our mailing list, or post them on phabricator. (You can also find the KSyntaxHighlighting framework on github for convenience, but it’s not our primary platform).

You can also support Kate and the KDE Frameworks by donating to the KDE e.V., KDE’s non-profit organization.

Bug fixed after 13 years

During the Randa sprint an 13 year old bug was fixed 😛

I myself moved it to kxmlgui (out of Kate/KWrites’s harm, good to delegate stuff away 🙂 in 2003 and since then we got a lot of duplicates but never somebody got the time to track it down. (333 votes for it, really nice number)

Now, after 13 years, it got done (and yet another chance that a bug becomes a sentient intelligence has vanished ;=)

Bug 64754 – XMLGUI items (toolbar icons, menu items) from merge sections move or disappear

Thanks to David, Dominik and Sune to get this fixed ;=)

And I really like the comment we got after the fix, awesome:

David Faure, you deserve a medal.

A 13 year old KDE bug finally fixed. Just think, when this bug was first reported:

— The current Linux Kernel was 2.6.31

— Top Movie? The ORIGINAL Underworld.

— Windows XP was the most current desktop verison. Vista was still 3 years away.

— Top 2 Linux verions? Mandrake and Redhat (Fedora wouldn’t be released for another 2 months, Ubuntu’s first was more than a year away.)

— Top billboard song? Crazy In Love by Jay-Z & Beyoncé (who was barely old enough to drink)

— 3 of the 5 KDE ev board members hadn’t ever used KDE

— Palestinian Prime Minister Mahmoud Abbas resigns ending “Road Map for Peace”

— Current KDE version? 3.1.4 (KDE 3 had only been out for a year)

Very very cool!

Not sure if the kernel version is right, more likely some < 2.6.0 kernel was the king of the hill at that time, but otherwise, great 😛

Therefore: Support us, Randa sprint and other sprints really bring our software stack forward! Nowhere else such a nice group of KDE developers can meet up to solve such problems together!