Subscribe to Planet KDE feed
Planet KDE -
Updated: 39 min 4 sec ago

Krita Receives Artist Choice Award from ImagineFX

Fri, 2015/01/02 - 5:55pm

Make sure to check out the January 2015 issue of ImagineFX where Krita receives the Artist Choice award! That’s appreciation with a vengeance!  ImagineFX is the #1 resource for concept artists and illustrators in the entertainment industry. It is a great resource if you are looking to level up your art skills.

You can pick up the January 2015 issue at newsstands or on the website. The USA distribution takes a bit longer to arrive, so you might have to wait a bit before you see it in places like Barnes & Noble.

digiKam Recipes 4.3.1 Released

Fri, 2015/01/02 - 8:53am

I ring in the new year with a digiKam Recipes update. This version features two new recipes: Remove Keywords from Photos and Add Web Interface to digiKam with digiKamWebUi. In addition to that, the updated and expanded Deal with Bugs in digiKam recipe now explains how to generate backtraces.


Continue to read

Retiring Plasma NN 0.9.0.x

Thu, 2015/01/01 - 8:53pm

I am in the process of retiring Plasma NM 0.9.0.x (aka old Plasma NM applet). The new applet (Plasma NM >= 0.9.8.x) is already shipped with all major distributions. I may release Plasma NM with some few bugfixes if someone is interested in that. However after there will be no further releases for the old applet. It will enter in unmaintained state and I will ask sysadmin to remove/disable NetworkManagement product from There is already product plasma-nm to report bugs in the new applet.

What's going on with measures in Marble

Thu, 2015/01/01 - 12:09pm

Here in the Marble world, we are working hard on expanding the current functionality with new features. Today I would like to show you some stuff we’ve recently introduced as part of the Measure tool. The measure tool is basically a multifunctional georuler, that allows to perform a variety of measurements. For instance, now you can easily measure distances on trivial paths or areas of complicated polygon shapes.

Polygon Ruler: LondonMeasuring area and perimeter

BearingsMeasuring angles between path segments

The polygon mode has a few options to enable: distance, bearing, bearing change, area and perimeter. The bearing is an angle between the North and the direction of movement. The bearing change is basically an angle between two path segments. All values are calculated for spherical Earth, so it should work for most cases.


Circle Ruler


The Circle mode offers radius, area and circumference features here. That’s enough for most cases. In the Circle mode, you obviously can put only two points, the first is the center of the circle and the second one lies on it.

You also can switch the current mode (Polygon/Circle) and enable/disable specific features in the Measure Config Dialog: Dialog

All new features have been developed by Sergey Popov (Sergobot) and me. Needless to say, what we see now is not the final “polished” version. It obviously needs some visual UI tweaks, these will be added soon, after a massive refactoring. From other topics that are being covered at the moment, priority takes Touring, Map Editing (EgorMatirov), OSGeoLive integration & packaging (Sergobot) and of course, bug fixing.

Happy New Year!

KDots 0.5.2 released

Wed, 2014/12/31 - 5:38pm

About 2 years ago I have started one project in KDE Playground called KDots. This is an implementation of the game of dots.

In this game players are trying to catch opponent’s dots by placing their dots on the game board where the lines cross. Possibly it looks like Go I suppose :).


Because of some reasons I abandoned KDots. And it has been left in the Playground up to this days with several known bugs and not so smart AI.

A week ago, I decided to come back to this project, and looks like two years ago I was a very horrible programmer, because the code couldn’t be read without facepalm, therefore I decided to redesign an architecture of the application and make fixes to stabilize it for a start.

All these changes have been included in the bug fix release 0.5.2.

Currently a players can play KDots on the same PC, through internet connection or with AI.

Many items still are in TODO list: * New AI * Saving game state * More pleasant UI

If anybody in the community can make any advice about possible improvements, your helps are welcome.

Source code can be downloaded from git :)

Round 2

Wed, 2014/12/31 - 5:20pm

Well the first two laps of my first SoK is over and now I finally enter into the final lap. In the first month I had finished with the design of the site but it was just plain and simple HTML/CSS and as we all know that is not enough. So the next question that arises is – what do we need ? And the answer to that will be a framework.

As my aim is to make a site that will be used for a long time and to enable that editing and updating information should me made easy and hence I have used wordpress to enable the same.

This months main challenge was to convert my HTML/CSS webpage into a wordpress theme. As I am a newbie to wordpress hence it was quite a humongous task for me but I as successful at the end. I converted my theme and imported all the old news on to my wordpress instance.

Click here to get a look at the site now.

As you might correctly notice that there are some images missing in the latest article section. That is the area I am currently working on. Once that is done then 99% of my task will be completed.

My only regret is the lack of communication between me and my mentors this month. When I am stuck at certain issue I remain stuck for a long time till I somehow complete it.

[SoK] Cantor Python backend status update

Wed, 2014/12/31 - 12:46pm

There were not many commits from my side to the Cantor project during the last month, but most of stuffs that are related to porting the Python 2 backend to Python 3 have been done.

In the next month I’m going to cover all these code by tests and try to fix existent bugs in the KF5 branch.

At the end, I would like to thank Felipe Saraiva, Pino Toscano and Alexander Rieder for the help that they have done during the SoK.

Happy New Year to all KDE community members.

2014 and 2015

Wed, 2014/12/31 - 12:03pm

In just a few hours 2014 ends. This is a great opportunity to look back at what happened this year in the ownCloud world and in my personal life. This was an absolutely crazy 12-month so this blog post is now way longer that I planed. A huge thanks you to everyone in the ownCloud community. It´s a blast to work together with so many clever and friendly people from all over the world.

ownCloud 7
First and most importantly we released ownCloud 7. This was a major milestone in the history of ownCloud because of several reasons. We made significant improvements in the area of quality and overall polish. The user-interface was refreshed and we implemented a ton of improvements all over the place. You can have a look at the feature page if you are interested:

But ownCloud 7 was also the first release which featured a big and strategic new direction for us which is server 2 server sharing. This is the first step to build a truly distributed and federated and open cloud. In my opinion it´s the future of a self controlled and self hosted cloud world, which respects privacy. But also enabled easy collaboration and sharing. ownCloud 8 will be another big step forward in this direction but this is something to discuss in 2015.

ownCloud Inc.
ownCloud Inc., the company behind ownCloud, grew significantly in number of customers and revenue. We opened up several new offices and hired a lot of new employees. This is very exiting for me because it´s so much fun to work with so many smart and dedicated people on ownCloud. I´m super happy to see how employees and community volunteers work together to push ownCloud forward.

ownCloud community
The ownCloud community is the source and foundation of the ownCloud development. I´m super happy that we are growing significantly and that more and more people join us to drive ownCloud forward. We use Bitergia to measure some community metrics. You can look at the statistics here:  Jos blogged about this last summer and we had close to 300 contributors in the past 12 month at the time. This is a very impressive number and ownCloud is already one of the biggest open source projects out there. But if you look at the statistics today than you see that we already grew to 372 contributors in the last 12 month since August in the meantime. This is just amazing. So I´m sure that everyone who wants to contribute to ownCloud finds a very friendly and open community to join. Let´s make the world a bit better together.

Lately we launched the new ownCloud Meetup program. Everybody is invited to start local ownCloud meetups and get-togethers.
We provide a lot of  useful helpful information on our website and you will get support if you want to organize an ownCloud event in your area. More information here:

We also launched the ownCloud insiders program if you want to help to promote ownCloud
The ownCloud community will be at FOSDEM and SCALE next year with tables. So if you are at one of the events please stop by and say Hi :-)

In the past a lot of people asked about the license of the ownCloud iOS app. So I´m super happy that a few weeks ago we found a way to open source the app. So everyone who want´s to contribute has now the opportunity:

ownCloud contributor conference
Last summer we organized our yearly ownCloud developer meeting in Berlin again. Because of our growing community of contributors we were able to transform this into the very first ownCloud Contributor Conference. Over 100 contributors joined to listen to talks, discuss, write code and socialize. You find some impressions here: This was a crazy event. Especially if you remember that the very first ownCloud meeting in 2010, just four years ago, had only 5 attendees.

A few days ago I learned that the Linux Journal readers voted ownCloud as number 4 of the best new open-source projects and number two of the best cloud based file storage solution. This is very exiting because only Dropbox is more popular at the moment that ownCloud.  The gap is shrinking fast compared to the numbers of last year.
A few days ago I learned that I won the Stiftung Neue Allmende award for starting and maintaining ownCloud which is endowed with 550,- EUR. This is a huge honor. Thanks a lot for that. Obviously ownCloud is not only developed by me but by our community. So I will donate this to the ownCloud community. We will use this for a nice social event at the next Contributor Conference next summer. Yay! Thanks a lot again :-)

2014 was also a special year for me personally. I moved to Boston, MA last spring to be able to work closer with my colleagues in the ownCloud Inc. headquarters in Boston. This is definitely fun and an interesting experience to live in the US full-time. I also took the opportunity to buy a motorcycle again which is awesome. I have a lot of fun with discover the great nature in New England by bike.

I also had the opportunity to meet very interesting people like Tim Berners-Lee, Linus Torwalds and RMS to discuss ownCloud and it´s great to hear that they all like it. What is also very exiting for me is that we are also working closely together with very clever people from the W3C offices at MIT Cambridge and CERN in Switzerland to develop innovative technologies that will hopefully land in ownCloud next year.

I also did a ton of travel last year to give talks and keynotes at conferences all over the world. Most important for me was the invitation the give a keynote as LinuxCon Europe about the future of cloud computing and federated clouds. This was a good opportunity to share my vision about distributed and federated clouds with a broader audience.

So what are the plans for next year?
The next big milestone is obviously ownCloud 8. Feature freeze is today the Dec 31th with a planed release date of early February. ownCloud, the software and the contributor community, reached a size where big monolithic releases don’t work anymore. The release of 7 was already very hard to coordinate, stabilize, test and to document all the features. So in the future we want to reduce the size of the core ownCloud server again and also release it more often and move to a time based release schedule.

So starting with ownCloud 8 we will release a major new ownCloud server version once a quarter. The apps on top should be compatible between different server versions and will be partly released independently.

On January 17th is the 5th birthday of ownCloud. At that day I announced the ownCloud initiative during the CampKDE keynote in San Diego. A bit later I released the first beta version and the first contributors joined. It’s amazing to see what grew out of a crazy idea. Does someone has an creative idea how to celebrate this special day? Please let me know.

Another important topic for next year will be the launch of the user data manifesto 2.0.  Hugo , Jan and I are working on this and a first draft is already out.
We got a lot of feedback from smart people and organization that we already incorporated. Everyone is more than welcome to participate in the discussions.

Thanks to everyone who made 2014 such a great year. I´m looking forward to keep on working with awesome people in 2015 again to push ownCloud and the ideas behind it forward. Let´s make the world a little bit better together.

Thanks and take care in 2015

Yet another way to make your app support StatusNotifierItem

Wed, 2014/12/31 - 11:49am

Yesterday I was notified of this little neat project:
(And yes its author would be very happy about feedback patches and so on ;)

Basically it’s a pure C++ library with very few dependencies that implements the support for StatusNotifierItem enabling systemtray icons in KDE Plasma 5 and Ubuntu Unity.
recomonded to be used by C++ applications that don’t actually depend from Qt or GTK and want to keep their dependency footprint very small (it’s Mit licensed so should be ok to use it from an app based on any license)
So now there are officially no excuse to not use our new shiny system tray ;)

MUP, a Markup Previewer

Wed, 2014/12/31 - 9:11am

Following up on my decision to promote more side-projects, here is a new one: MUP.

MUP is a markup previewer. It supports multiple markup formats. You can use it to read markup text, but it is also useful when writing markup text to check how your work looks, thanks to its refresh-as-you-save feature.

MUP in action

  • Supports multiple markup formats, easy to extend
  • Automatically refreshes itself when the document is modified, tries to retain the position in the document after refreshing
  • Skips metadata headers, such as those used by static blog generators like Jekyll
  • Supports gzipped documents, useful to read documentation shipped with Debian packages
Supported Formats

MUP supports Markdown and reStructuredText using Python modules.

It also supports other formats using external converters. External converters are command line tools which are invoked by MUP to convert input files. To be used as an external converter, the tool must accept markup on stdin and produces HTML on stdout.

Right now, MUP supports the following converters:

  • Markdown variants (you can never have too many Markdown parsers!):
    • Pandoc Markdown
    • GitHub Flavored Markdown via Kramdown
    • CommonMark
    • Gruber original Markdown
  • Man pages:
    • Ronn
    • Groff
  • Asciidoc

Adding a new converter is only a matter of creating a yaml file to describe its command line and the files it works with.

Sounds Familiar?

You may have heard about this project as "mdview". It used to be named like this but I renamed it because a) it supports more than Markdown and b) there are at least a dozen projects named "mdview" on GitHub :)

Want It?

MUP is on GitHub: git clone it and follow the instructions from the Install section of the README.

Flattr this

[SoK] Cantor Python backend status update

Wed, 2014/12/31 - 2:46am

There were not many commits from my side to the Cantor project during the last month, but most of stuffs that are related to porting the Python 2 backend to Python 3 have been done.

In the next month I’m going to cover all these code by tests and try to fix existent bugs in the KF5 branch.

At the end, I would like to thank Felipe Saraiva, Pino Toscano and Alexander Rieder for the help that they have done during the SoK.

Happy New Year to all KDE community members.

Knetwalk running on KF5 :)

Tue, 2014/12/30 - 2:18pm
With this screen shot i think my work of porting knetwalk is complete. I would like other kde members to test knetwalk's framework branch and report if they are experiencing any issue installing it on kf5. I will try and fix that error on my part.

SOK Project – Kanagram-Introducing 2-player option #3

Tue, 2014/12/30 - 1:56pm

Well, It’s almost been a month working on the application, and its been an amazing experience.
There has been changes made to the UI, like adding icons and texts so as to aide the user to interchange between the modes.
Also, the coding for it is done, but it needs to be worked on, as it is not working as supposed to. Mentor Jeremy Whiting, has been very helpful, and it feels great to work with him on this project.
What remains to be done is to keep track of the scores, when in the new mode.
I have my own clone of the main repository where I push my changes which is at:

Next update soon. Till then.

January Bug of the Month

Tue, 2014/12/30 - 12:45am

The KDE Gardening Team selected the January “Bug of the Month”. Before announcing it, let me write more about this initiative.

When I blogged about the nomination of the first bug, I probably left the impression that each bug is to be resolved in a time frame of one month. The bugs that get selected are often unresolved for a long time, and solving them might overlap with the announcement of the next bugs, so some patience is needed. But I have good news!

The first bug (Bug 324975: Volume gets restored to 100% after each knotify event) has been resolved thanks to the work of Albert Astals Cid. Because of translation changes, the fix will be available in the next KDE Applications release in April.

Regarding the second bug (Bug 288410: KDE daemon kded4 crashes on wake up), we already have a patch to test. There are packages available for openSUSE and Kubuntu, and Fedora packages are being prepared. Please check the recents comments in the bug report and give feedback.

But now to the bug for January. This time, a memory leak was selected.
It is Bug 271934: KDE daemon kded4 grows on memory usage

Reasons for the nomination:

  • the bug is the most reported memory leak in our bug tracker,
  • some people reported growth rates beyond megabytes per minute,
  • having to restart just to keep a low memory usage is annoying,
  • there was growing interest recently (raising CC list size),
  • getting more developers to try Milian’s new heaptrack tool.

If you are able to fix it, you will receive a honorable mention in the next issue of my blog post “The Bug of the Month” on Planet KDE.

Not all developers that would be able to fix it are subscribed to this bug. If you know someone, feel free to point them here.

KDE: SoK Progress report

Mon, 2014/12/29 - 11:44pm
Jenkins SoK KDE project

Jenkins SoK KDE project

This month has been very busy! I juggled the holidays with the following progress on my project:

Resolved the docker SSH issue.
Created and commited all of my functioning Dockerfiles for master and slave to my git repo.
TO-DO: Currently I only have a ubuntu slave, I would like to create a few distro slaves.
Created backup and restore scripts for that data volumes.

Finished Linux through frameworks. Holding to start the next phase of the project. I <3 Linux, was so easy.

Got OSX past qt5 and working through frameworks.
TO-DO: Problem point with kauth as the dependency to polkit-qt-1 is hard coded but Linux is the only platform that needs.
It seems silly to me to patch the code on the slave side as Windows will face the exact same problem, I think it should be fixed upstream and
I will pursue this route, perhaps I will get brave and create a patch to submit myself.

After much blood, sweat, and tears I got Windows past qt5, only for it to fail on the first tier of the frameworks.
TO-DO: Figure out why and fix it.

I am starting on the next phase and final phase before deployment. I need to research and pick a DSL system to dynamically load projects into Jenkins
on commit to a jenkins configuration repo. Basically we should only have to add a few variables and commit and Jenkins will load up the job and start it.
It will be great! Alas another learning curve for me, but I can do it!

Till next time.

Processed in digiKam Call for Submissions

Mon, 2014/12/29 - 12:18pm

Sharing is caring, right? So if you use digiKam for processing photos, why not share your photo editing techniques and tips with other users and showcase your best photos? I invite you to participate in the new Processed in digiKam feature on the Scribbles and Snaps blog. Continue to read

The Innovators by Walter Isaacson

Mon, 2014/12/29 - 10:51am

I just want to mention The Innovators by Walter Isaacson. I loved that "How a group of hackers, geniuses, and geeks created the digital revolution" began with Babbage and Lady Lovelace.

We're familiar with many of the people and projects Isaacson discusses, but there were many people of whom I knew nothing. Vannevar Bush, for instance, and his prophetic essay, As We May Think in July 1945.

What I appreciated most was the focus on collaboration. Time after time "lone geniuses" labored alone, and saw their work die with them. The work that lasts is done by teams of people who both inspire and perhaps annoy one another, but manage to bring their skills and  best selves to the group effort.

A good read.

Major Release

Mon, 2014/12/29 - 3:34am

It’s been awhile since my last smoke signals here in Planet KDE. I’d been quiet, a bit outdated on KDE things, focusing some efforts and calming down my heart for being so long away from this amazing community. What I’ve been doing, you ask ? Well, after six long tiring years, I’ve finished my Ph.D. in Computer Science last week. The defense was quite smooth and it’s rewarding to know that you did your best and left the game glad about the work you’ve done.

Doing a Ph.D. is experienced differently by different people. I’ve learned to exercise my patience, to be more pragmatic about my goals, to cope with my anxiety … I’ve survived and got away several times from The Valley of Shit :), met some deplorable Ph.D’s and another inspiring ones.


Although I’d been using Qt and KDE since 1999-2000, it was only in 2008 when I became more seriously involved in KDE. I was already in academia and that gives you the chance to meet some insane ;) students like Tomaz Canabrava.

Since then, we had a lot of things to be proud of: we made nice friends around the world, we strengthened local KDE communities in Brazil, we’ve been representing KDE for seven years in a row in major FLOSS Brazilian conferences. There were countless talks, short courses, hunting for new contributors, the first Akademy-BR and two LaKademies. That makes me happy but I’m, above all, a programmer. I’ve been missing the commits I haven’t done, the features I haven’t implemented and the bugs I haven’t fixed. I joined KDE already chased by that voice: “you have a Ph.D. to complete …” and it’s quite easy to let your passions dominate the priorities of your tasks :) I’m not saying that I hated my Ph.D. research topic. Not at all. But KDE took me like a burst of passion :) I’m glad I did not give up of my academic carrier and this “major release” makes me free to experience being part of KDE in a different way. So, the bottom line is: you can count on me for KDE in 2015 :) I just need some couple weeks for getting some rest.

For those of you who are wondering about what I’ve done in my research, it’s mostly related to automating the design of architectures for a sort of software-intensive systems named self-adaptive systems (those which regulate themselves in response to changes in the operational environment and in the software itself). We focused on a particular class of self-adaptive systems that adopts control theory as its underlying self-managing mechanism. We proposed a generic meta-modeling language (named DuSE) for systematically capturing the prominent design dimension in such a domain and applied techniques from multi-objective optimization field to reveal those candidate architectures that minimize/maximize some quality attributes of interest. We’ve been using our approach to generate effective self-managing architectures for self-adaptive web servers and elastic cluster platforms for MapReduce applications. Further information may be found here and here.

Two development outcomes of my research are directly related to Qt and KDE: the QtModeling and QtOptimization Qt5 modules and the DuSE-MT tool. QtModeling provides the basic features for handling software models and serializing them by using the XMI format. It also implements the metamodels of MOF, UML, and DuSE modeling languages. QtOptimization is an application framework for solving multi-objective optimization problems. So far, only the NSGA-II evolutionary algorithm is available, along with a bunch of common operators for selection, crossover, and mutation. DuSE-MT is a tool that integrates the features provided by QtModeling and QtOptimization in order to evaluate the approach I proposed in my Ph.D. thesis. Its architecture, however, was conceived to support the seamless integration of new features. Now, the plan is make the last polishments to have a first release of such modules. After that, maybe you can expect some model-related new features in Qt Creator and KDevelop :) or an even more shining Umbrello :).

Well, that’s all for now, but just for a while ;)

See ya,

The Christmas break project - autocompletion of KDE projects for kdesrc-build

Sat, 2014/12/27 - 4:26pm

kdesrc-build is an awesome tool used a lot around KDE - basically it's an automated build script to which you can just throw any git url and it downloads, configures, builds and installs the project for you. All that plus nice logging features on top. You can read some more over at Jeremy Whiting's recent blogpost.

What I missed for long long time is to have KDE projects autocomplete-able within kdesrc-build so that I don't have to guess or type the exact project names every time. Because on each run kdesrc-build downloads the kde_projects.xml file, the projects database is all there, ready to be used.

So I finally sat down and wrote a simple (and probably all wrong) bash autocompletion script. Now you can just type "kdesrc-build [tab][tab]" and have a list of all KDE projects \o/

As bash scripting is not my cup of coffee, I've put it in a wiki so that people more skilled can easily improve or extend it as they see fit (it would be great if it could autocomplete also the modules you have set in your rc file). I'll leave it to mature there for a bit and then I'd like to move it to the Techbase pages about kdesrc-build. For now it's using xml2 to parse the xml file, so be sure to have that installed.

Get it & edit here:

11 years developing Krita

Sat, 2014/12/27 - 2:37pm

This post was orignally planned as my 10 year anniversary post, but due to me finishing my thesis and starting on my new job this got a bit delayed and now I’m already 11 years on the Krita team. Boudewijn has already posted a much more detailed look back at the history of Krita. Here just some of my thoughts on the last 11 years.

I started working on Krita in late December 2013.  The funny thing is that I’m not an artist and I don’t really have a use for the application itself and was more interested in the development of a graphics manipulation in general. Ironically my art teacher back then claimed that you could not do art with the computer because there was not direct connection between the hand and the canvas and therefore the machine had more influence than the artist.

Back in 2003 Krita had never been released and the application was only able to do some very crude painting. I think the main reason that I started contributing to Krita back then was that I was much more comfortable with the single window UI and the fact that it used Qt/KDE and C++. In the early days I would never have imagined that I would be still with the project after 10+ years and how big the project is now. Even that the project exists today is a miracle and result of many developers putting in effort without ever knowing how it would develop. For the first few years we had almost no users and the users that we had were die-hard KDE users. At the time that wasn’t a bad thing as it allowed us to do some radical changes and experiments. Many features that were developed during this time still provide the base for the current Krita.

The early days of development were a bumpy ride. We made three releases based on Qt/KDE 3 and Krita was starting to take of with version 1.6. Then we made the jump to KDE 4, which was expected to be big, but in hindsight turn out much bigger than anyone was expecting. In the end it took several years to complete that and if we had known how long it would take we wouldn’t even have started that. During that period the project the suffered quite a bit as development stalled for some time and we lost some developers which got exhausted from the port. The biggest things we learned from that is to never start porting to a new set of libraries before it’s even tested,  to never make a release cycle longer than a couple of months and when you are porting to never do anything but porting.

After Krita 2.0 was released we got back on track and made good progress. Releases happened much more frequently still the improvement from version to version became bigger and bigger. Looking back it’s interesting how old even the last version looks. One of the major turning points in this time was the decision to concentrate on painting in Krita. Back then it was a big controversy, but today I think it was maybe the best desision we ever made. It sharpened the development and made Krita overall a better application. I think we proved the everybody wrong who said that we focus on a too small user group. Based on bug tracker and forum activity we certainly have at least a tenfold growth of the userbase since then.

The current development of version 2.9 is really exciting. This version will bring support for multiple-windows inside the application which is one of the biggest changes we ever made to the user interface. Also really nice it that the 2.9 beta is attracting a lot of user testing. Several years ago I made a post about Krita needing more bug reports, now we got in the last two weeks more bug reports for the 2.9 beta than we got in a whole year back then.



For the future there is a lot of interesting stuff coming up. Due to my new job I won’t be able to contribute as much as I used to, but I will continue to work on Krita. After 2.9 we will make the jump to Krita 3.0 which will use Qt 5/KDE Frameworks 5. The new libraries are not that interesting I think as in terms of desktop development not much changed since the  KDE 3 days. For some users it will mean less dependencies which will certainly close some discussions. I think the developments I’m looking forward to in 2015 are Level of Detail painting (which should bring us up to Photoshop speed) and animation support which is one of the most requested features. Both have already seen some initial development, but will need more work in 2015.

I want to thank every developer who ever worked on Krita and all the users who supported us.