KF5 on dennogumi.org

Danbooru Client 0.2.0 released

Sun, 22 Feb 2015 20:38:02 +0000

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):

Sometimes they come back: Danbooru Client ported to KF5 and C++

Sun, 15 Feb 2015 21:59:37 +0000

Some of you may remember a semi-complex application I wrote back in the days, namely 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.

Latest 4.13, newest 4.14 beta and Plasma 5 in openSUSE

Wed, 16 Jul 2014 05:43:49 +0000

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.

Changes in KDE Frameworks 5 and Plasma 5 packaging in openSUSE

Sat, 28 Jun 2014 11:59:23 +0000

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.11.x Plasma Workspace. The move was made to ease maintenance and packaging, as it meant dropping a number of hacks, and also to make KF5 + Plasma 5 packages suitable for inclusion in openSUSE Factory. At the same time, the 4.11.x workspace packages were adjusted to reduce the number of components conflicting, so that applications depending on workspace libs (such as KDevelop) would remain on the system also with P5 installed.