Below you will find pages that utilize the taxonomy term “KF5”
February 22, 2015
Danbooru Client 0.2.0 released
After my previous post, development went quicker than expected, so I’ve actually managed to get a real version out. ;) So without much ado… here’s Danbooru Client 0.2.0!
This redesigned C++ version brings a few more features compared to the PyKDE4 version, notably:
Infinite scrolling (experimental) - Just scroll down to load the next set of posts QML-based thumbnail view Click on the image below to have a demonstration of what’s in this release (warning: 2M GIF file): [!
February 15, 2015
Sometimes they come back: Danbooru Client ported to KF5 and C++
Some of you may remember a semi-complex application I wrote back in the days, namely [Danbooru Client]({{ site.url }}/projects/danbooru-client/). Written in PyKDE4, it provided a semi-decent interface to Danbooru-style boards. It mostly worked and received little maintenance (also because I didn’t have that much time for maintenance).
In the mean time, I started learning some C++. No, it’s not that I don’t like Python (in fact I do, I use it a lot in my day job), but I wanted to gain at least some basic skills to be able to contribute directly to KDE software.
July 16, 2014
Latest 4.13, newest 4.14 beta and Plasma 5 in openSUSE
Congratulations to KDE (of which I’m proud of being a part of) for the newest release of the Plasma workspace! At the same time, the 4.x series has seen a new beta release, and the stable branch got updated, too.
I’m betting a few people will ask “Are these available for openSUSE?” and of course the answer is yes, thanks to the efforts of the openSUSE community KDE team and the Open Build Service.
June 28, 2014
Changes in KDE Frameworks 5 and Plasma 5 packaging in openSUSE
Since a couple of weeks the packages offered by openSUSE in the KDE:Unstable:Frameworks repository have undergone a series of changes. In particular, the packages now install to /usr. For the libraries (KDE Frameworks 5) this will mean a transparent change for the userbase as they are expected to be co-installable, but the workspace components (Plasma 5) will confict with the existing Plasma 4.11.x installation.
What does this mean in practice? If you want to use Plasma 5 you will not be able to use a 4.