Full de ruta del Krita de 2026

En dues sessions, els desenvolupadors del Krita va debatre en què volen treballar el 2026, després que es publiquin el Krita 5.3 i el Krita 6.0. Això és, en realitat, un llançament, però una versió es construeix amb les Qt5 i una amb les Qt6. El llançament està previst per al mes vinent.

Interfície d'usuari d'esbós del Krita

L'any passat, Timotheé va crear un prototip per a una interfície d'usuari mòbil per al Krita (hi ha un APK que podeu instal·lar per a jugar). Al mateix temps, Wolthera va acabar el seu treball en la forma de text nova i les eines de text. Ambdós projectes utilitzen les característiques del QML i el QtQuick de les Qt per implementar la interfície d'usuari.

Aquest any, pretenem treballar en la substitució dels acobladors d'opcions d'eina amb el QML perquè puguem utilitzar-los tant en el mòbil com en la versió d'escriptori del Krita.

Alvin Wong va experimentar el 2025 amb la incrustació d'un llenç basat en OpenGL dins d'una aplicació QML. Dmitry i Carsten continuaran amb aquesta feina i veuran si es pot utilitzar el llenç del Krita per a mostrar una imatge dins del prototip del Timotheé.

Agata ja ha començat a treballar per fer que la interfície d'usuari actual sigui més adequada per a l'ús de tauletes.

Treballar amb fitxers

There are a couple of plans we have with regards to file handling. On Android, working with the file sandboxing is seriously complicated, and we're looking into a solution for that.

The Krita .kra file format is pretty old by now (not 25 years, since it came into being a few years after Krita started being developed). It can, obviously, load and save everything Krita can handle, but it is not a particular fast file format. Carsten proposed to look into an SQLlite based file format. This could potentially mean that we could save the image after every change without the user noticing, making saving completely transparent.

Agata is already working on improving the autosave dialog. There is already a mockup for this.

Ivan is looking into sharing settings and resources across a user's devices, ideally in a cross-platform way.

Color Management

While Krita supports HDR displays, there are issues with the user interface. Wolthera wants to start improving there.

Now that Qt 6 includes support for color management, CMYK and higher-bit depth images, it should be possible to add color management to Krita's vector layers, and that's something we are eager to implement.

We also discussed Wayland. We now support color management on Wayland on Linux, but there are plenty of problems there. We decided to only support the KWin Wayland compositor that comes with KDE Plasma for now.

Performance

Dmitry wants to work on "region based updates", and has already started on that: this will make working with large images faster.

Ivan and Wolthera are interested in using vectorization in filters, possibly replacing the use of LittleCMS for color transformations.

Continuous integration

Continuous integration is how we build Krita: after changes, Krita is built automatically for every platform. Now that we've access to Windows ARM hardware, we need to find a way to extend our builds to Windows ARM, but the CI factory doesn't have an ARM builder, so we'd need to cross build.

We also intend to update all Krita's dependencies to the latest version, but only after we release Krita 5.3 and Krita 6.0. And of course, we intend to keep releasing bugfix and feature releases this year! For now, Krita 5.3 is the standard release, and 6.0 is considered experimental, but that should have changed by the end of the year.