Mapa de desenvolvimento do Krita em 2026

Em duas sessões, os desenvolvedores do Krita discutiram o que pretendem desenvolver em 2026, após o lançamento do Krita 5.3 e do Krita 6.0. Na verdade, trata-se de um único lançamento, porém uma versão será desenvolvida com Qt5 e a outra com Qt6. O lançamento está previsto para o próximo mês.

Esboço da interface do usuário do Krita

No ano passado, Timotheé criou um protótipo para uma interface de usuário móvel para o Krita (há um APK que você pode instalar para experimentar). Ao mesmo tempo, Wolthera terminou seu trabalho nas novas ferramentas de forma e texto. Ambos os projetos usam os recursos QML e QtQuick do Qt para implementar a interface do usuário.

Este ano, pretendemos trabalhar na substituição dos painéis de opções de ferramentas por QML, para que possamos usá-los tanto na versão móvel quanto na versão para desktop do Krita.

Em 2025, Alvin Wong experimentou incorporar uma tela baseada em OpenGL dentro de um aplicativo QML. Dmitry e Carsten darão continuidade a esse trabalho e verificarão se é possível usar a tela do Krita para exibir uma imagem dentro do protótipo de Timothe.

Agata já começou a trabalhar para tornar a interface de usuário atual mais adequada para uso em tablets.

Trabalhando com arquivos

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.