 Okay, the next speaker is going to be Volker Kraus from KDAB. He's going to be talking about colorful text in your favorite text editor, or specifically about KF5 syntax highlighting framework. Volker, ready when you are. The mic's not. Yeah, I don't have anything remotely as cool to show, just some refactoring we did in 20-year-old code. Yeah, I mean, syntax highlighting is something we take for granted whenever looking at some form of structured text in any way, right? And the solution we have for that in KDE has been since almost 20 years, Kate, and the syntax highlighting engine built into that. That, yeah, is an abstract engine that is fed by XML files describing the actual syntax. And that was actually one of, I think, KDE's first success stories in terms of user-generated content predating the Get Hot New Step framework, resulting in, by now, I think, what is it, 270 syntax definitions for anything common or uncommon you can find out there. And it's really old and solid, well-tested code. The only problem with it is if you want to embed that into your own application, and that's where I got involved there, because I, of course, wanted that in gamma ray when looking at some shader code fragments. The implementation is very heavily tied to the Kate editor. But at least that is, I mean, Kate editor is available as a plugin, the Kate part, that can be embedded in applications, and that's what Kyle and Kate developments all do, but it requires the XML GUI framework in order to enable that. For my use case in gamma ray, that would have been, well, more than a minor inconvenience to refactor the entire main application to make that possible. But besides the standalone application, we also have a Qt Creator plugin. And, I mean, try to explain the Qt Creator team that they need to switch to XML GUI so that a plugin of a plugin of theirs can have syntax highlighting for a bit of a shader fragment. So that's not going to fly. And yeah, what we then started, actually, last academy together with Christopher and Dominic is to extract the engine that is in Kate and make that a standalone Tire 1 framework. And make it independent of how and where you are going to use it. So you can use it for the full-featured editor where you tie it then to the internal structures all the way to just generating formatted HTML output. So basically what you get in the API is you feed it text lines and it tells you from that offset to that offset, this is a keyword highlighted in whatever color your theme has selected. So that's the actual engine we have in the framework. We also have all these syntax definitions there. So this is now the canonical source for the XML files. The engine also provides code folding information so you can collapse entire blocks if your output format supports that. And we have the parts of the seeming data structures in there with, I think, two base themes, one for light and one for dark because you need to get the colors from somewhere that still look good on different backgrounds. But in terms of dependencies, this is Qt GUI only, nothing else. So really easy to integrate. You can use that for the full-editor use case. We also have a Q-syntax highlighter included for convenience which then enables you, if you have a Q-text document or Q-text edit, with just a few lines of code to leverage the full 250 or 270 different syntax highlightings in a normal multi-line text widget in your Qt application. I think we also have a command line tool that just generates HTML5 output originally supposed to be used for the testing, but it shows what you can now do with having the engine stand alone. Stuff I'm still waiting for and which should now also be very easy to do is mark a bit of code on a slide or in a text document, right-click highlight as C++ or highlight as JavaScript or whatever. Or email attachments, right? You get the C++ file, so I could have inline highlighting in Cayman. Those use cases, and even there, the Kate part embedding wouldn't have helped. And that's not possible. Yeah, I think that's it. Since I have to use Albert's laptop, I can't actually show it live. This is C++ code. I mean, it looks like what we are used to from Kate, including code folding even, but this is a Q-text edit with a Q-syntax highlighter. Well, and a bit of extra code for the line numbers and folding. And yeah, the actual highlighting is less than 20 lines of code, including the ability to actually have the full menu to manually select it and all of this. And it even does incremental re-highlighting, so if you do a block comment, it only updates the few following lines that are affected, making it even half way performant if you don't have the fully optimized editor for specifically that use case. Yeah, first release was then in October or November with Frameworks, and yeah, since then it's part of the Frameworks release therefore should be easily available for integration. Yep, that's it.