Tabella di marcia 2026 di Krita

In two sessions, the Krita developers discussed what they want to work on in 2026, after Krita 5.3 and Krita 6.0 are released. That is, actually, one release, but one version is built with Qt5 and one with Qt6. The release is planned for next month.

Interfaccia utente Schizzo di Krita

L'anno scorso, Timotheé ha creato un prototipo per un'interfaccia mobile per Krita (esiste un APK installabile per provarlo). Allo stesso tempo, Wolthera ha terminato il suo lavoro sulla nuova forma di testo e i relativi strumenti. Entrambi i progetti utilizzano le funzionalità QML e QtQuick di Qt per implementare l'interfaccia utente.

Quest'anno intendiamo lavorare sulla sostituzione delle aree di aggancio Opzioni dello strumento con QML, in modo da poterle utilizzare sia sulla versione mobile, sia su quella desktop di Krita.

Nel 2025 Alvin Wong ha sperimentato l'incorporazione di una tela basata su OpenGL all'interno di un'applicazione QML. Dmitry e Carsten porteranno avanti quel lavoro e vedremo se riusciremo a usare la tela di Krita per visualizzare un'immagine dentro il prototipo di Timotheé.

Agata ha già iniziato a lavorare per adattare meglio l'attuale interfaccia utente all'uso nelle tavolette grafiche.

Lavorare con i file

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.