Full de ruta 2026 de Krita

En dues sessions, els desenvolupadors de Krita van discutir en què volien treballar durant el 2026, després del llançament de Krita 5.3 i de Krita 6.0. En realitat, són un llançament, però una versió està construïda amb les Qt5 i l'altra amb les Qt6. El llançament està previst per al mes que ve.

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

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

Este any, tenim la intenció de treballar en la substitució dels acobladors «Opcions de l'eina» en QML per a poder utilitzar-los tant en la versió mòbil com a la d'escriptori de Krita.

L'Alvin Wong va experimentar el 2025 amb la incrustació d'un llenç basat en OpenGL dins d'una aplicació en QML. En Dmitry i en Carsten continuaran esta faena i veuran si podem utilitzar el llenç de Krita per a mostrar una imatge dins del prototip d'en Timotheé.

L'Agata ja ha començat a treballar per a fer que la interfície d'usuari actual siga més adequada per a l'ús en les 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.