While KDE Frameworks 5 was just released this week, there's already new features and functionality sought after for future revisions of this modularized set of next-gen KDE libraries.
Covered in yesterday's KF5 update meeting were many changes/features still being desired by KDE developers. Among the highlights of future work include:
- Ensuring there is proper tooling and it's easy for developers to get started for developing applications on KDE Frameworks 5.
KDE 4.14 code is getting ready while being worked on for a December debut is a mix of KDE4 and KF5 application code.
The KDE 4.14 software code has been branched from master for all KDE Software Compilation repositories (sans KActivites that's being left out for a 4.14 release). In terms of what's next for the master code-base, while before a potential "KDE 4.15" release was talked about, it was agreed upon by KDE developers that 4.14 will be the last of KDE Applications that exclusively use KDE Platform 4.
We are happy to announce the Qt Creator 3.2 beta today. So you can already check out the many improvements we have done for the upcoming 3.2 release, and, not to forget, give us feedback on what we have so far. We mostly concentrated on stability and improvements, so no completely new platform supported this time, sorry . I’ll randomly highlight some of the changes here, but you should probably check out our change log as well for a more thorough overview, and just download the binaries and try it for yourself.
I’ve been wondering for quite some time though how the state of Plasma Next is when it comes to accessibility. In this case accessibility is mostly how the applications and desktop shell expose semantics to the accessibility framework via an API (on Linux the beast is called AT-SPI, a DBus API). The goal is that assistive technology such as a screen readers (Orca), the screen magnifier, or Simon can pick up what’s going on and assist the user. This allows for example blind people to use the software. The big thing here is that while Qt never had good support for QGraphicsView accessibility, we plowed away at making things work well with Qt Quick. This afternoon I finally got around to looking at the next iteration of the KDE desktop for real. In fact I’m writing this in a running Plasma Next session on top of the frameworks 5 libraries. It feels a bit like the porting from KDE 3 to 4, except that most things seem to just work so far.
This is the last but one update to the 2.8 series of the Calligra Suite, and Calligra Active released to fix recently found issues. The Calligra team recommends everybody to update.
Why is 2.8.4 skipped? Shortly before 2.8.4 release we discovered bug that sneaked in 2.8.2 version and decided to skip the 2.8.4 entirely and quickly release 2.8.5 instead with a proper fix. The bug is related to not showing file formats in Save dialogs.
Also: Calligra 2.8.5 Released
Linux Mint 17 ‘Qiana’ KDE and Xfce editions were released late last month, just a few weeks after the main editions (Cinnamon and MATE) were put out. This release will have the same lifespan as the distribution which is based on, Ubuntu 14.04 Trusty Tahr, so it will be supported until 2019, for no less than five years.
The KDE Community introduced the concept of convergence way back in 2008 with the arrival of KDE 4.x (back then it was still KDE Desktop). If you ever tried KDE on your netbook you would have noticed that the desktop that got installed was different from that you would get when you install the same iso on your desktop.
We just finished migrating one of our stacks to a new and powerful piece of hardware. It was a major activity and took about 9 hours with around 2-3 hours of downtime per CMS. The activity is now complete, however there are a few rough edges that we’ll be ironing out over the weekend.
Technically, the functions to reach those goals all bring their own interactions and workflows. For users it is necessary to perceive clearly what happens and how to achieve the desired result. Unfortunately, some uncontrolled growth in KDE applications has lead to non-standardized implementation and application-specific short-cuts.
A few weeks ago I contacted Thomas Pfeiffer with the idea to design a new user interface for Klipper in Plasma 5.1. Surprisingly he informed me that a discussion was already started in the KDE Forums. Which is awesome as that means there was already some ideas on how the user interface could look like. Last week the number of new bug reports for KWin get lower so I started to look into Klipper for 5.1.