As many readers of this blog are aware, openSUSE has been offering packages of git snapshots from KDE since quite a while. They are quite useful for those wiling to test, report bugs, and / or hack on the code, but also for those who want to see what’s brewing in KDE land (without touching their existing systems). However, a major drawback for non English speakers was the lack of translations.

(Note: this post also appears in Planet KDE and Planet openSUSE because I thought this might be interesting to others) As I mentioned in some other posts, I have a small “server” which I use as a NAS to provide archiving for photos and other files of interest. As it runs in a remarkably small (and quiet) enclosure, I’ve managed to put it in an incospicuous part of the room it is in.

The migration happened and well… it turns out that it was not as smooth as I expected. In particular, comments weren’t working at all due to a filesystem permission on the database (which meant nothing would get written at all). That is now fixed. Sorry for the problems. To add problems over problems, I had a hardware failure (RAID card) last June, which wrecked the root filesystem and I had to reinstall everything from scratch.

You might have noticed that the blog has a markedly different look than before. It has not only changed visually, but also under the hood. This (brief) post summarizes the reasons behind the change. Why? Simply put, the previous solution was unmaintainable. “But,” you might say, “it was a static site generator! How could it become unmaintainable?”. It can. You might recall I moved from Wordpress to Jekyll about six years ago.

If I look back at the last post I made on ths blog… let’s say quite a lot of time has passed. The reason? Well, first of all, one would call it a lack of motivation1, and afterwards, the emergence of a small yet quite annoying pathogen which caused a bit of a stir worldwide. But today I’m not going to talk about viruses: perhaps some other time when you can avoid hear about it for breakfast, lunch, and dinner.

Part of this post is about openQA, openSUSE’s automated tool which tests a number of different scenarios, from installation to the behavior of the different desktop environments, plus testing the freshest code from KDE git. Recently, thanks to KDE team member Fabian Vogt, there has been important progress when testing KDE software. Testing the Dolphin file manager Those who use KDE software, either in Plasma or in other desktop environments have at least heard of Dolphin, the powerful file manager part of KDE Applications (by the way, have you checked out the recent beta yet?

As you may already know (if you don’t, please check these older posts) openQA, the automated testing system used by openSUSE runs daily tests on the latest KDE software from git. It works well and uncovered a number of bugs. However, it only tested X11. With Wayland starting to become usable, and some developers even switching to Wayland full time, it was a notable shortcoming. Until now. Why would openQA not run on Wayland?

A new version of Danbooru Client is now available! What is Danbooru Client? Danbooru Client is an application to access Danbooru-based image boards (Wikipedia definition). It offers a convenient, KF5 and Qt5-based GUI coupled with a QML image view to browse, view, and download images hosted in two of the most famous Danbooru boards (konachan.com and yande.re). Highlights of the new version Unbreak konachan.com support (change in URL format) Coming up next HTTPS support!

In the past three weeks, the openSUSE community KDE team has been pretty busy to package the latest release of Applications from KDE, 16.12. It was a pretty large task, due to the number of programs involved, and the fact that several monolithic projects were split (in particular KDE PIM). This post goes through what we did, and how we improved our packaging workflow. Some prerequisites In openSUSE speak, packages are developed in “projects”, which are separate repositories maintained on the OBS.

Admit it: how many times you have seen “software from this branch is completely untested, use it at your own risk” when you checked the latest code from any FOSS project? I bet you have, many times. For any reasonably modern project, this is not entirely true: Continuous Integration and automated testing are a huge help in ensuring that the code builds and at least does what it is supposed to do.

You may be aware that openSUSE Leap 42.2 is now in the release candidate stage, and there’s a lot of activity aimed at squashing those pesky bugs before they hit the final release. One particular bug proved to be quite tough to fix, and it was only solved thanks to the “heroes” mentioned in the title. This is the history of the bug. The report October 6th, 2016 - A bug iss reported against Plasma reporting a hard freeze of Plasma when using the Noveau driver, but not with the closed NVIDIA blob.

As you may know (unless you’ve been living in Alpha Centauri for the past century) the openSUSE community KDE team publishes LiveCD images for those willing to test the latest state of KDE software from the git master branches without having to break machines, causing a zombie apocalypse and so on. This post highlights the most recent developments in the area. Up to now, we had 3 different media, depending on the base distribution (stable Leap, ever-rolling Tumbleweed) and whether you wanted to go with the safe road (X11 session) or the dangerous path (Wayland):

Every day, a sizable number of people posts problems on the KDE Community Forums and the ever-helpful staff does their best to solve whatever issues they’re facing. But what exactly does one do when this happens? This post provides more insights on the process. NOTE: The following applies to my workflow for the Kontact & PIM subforum. Step 1: Someone posts a problem The questions posted are various, and range from simple tasks (“how I do XXX”) to very specific workflows.

A new version of Danbooru Client is now available! What is Danbooru Client? Danbooru Client is an application to access Danbooru-based image boards (Wikipedia definition). It offers a convenient, KF5 and Qt5-based GUI coupled with a QML image view to browse, view, and download images hosted in two of the most famous Danbooru boards (konachan.com and yande.re). Highglights of the new version Support for width / height based filtering: now you can exclude posts that are below a specific width or height (or both) New dependency: KTextWidgets Coming up next Sooner or later I’ll get to finish the multiple API support, but given that there’s close to no interest for these programs (people are happy to use a browser) and that I work on this very irregularly (every 6-7 months at best), there’s no ETA at all.

Ever since the launch of Argon and Krypton, the openSUSE community KDE team didn’t really stand still: a number of changes (and potentially nice additions) have been brewing this week. This post recapitulates the most important one. I’d like the most recent Qt, please As pre-announced by a G+ post, the openSUSE repositories bringing KDE software directly from KDE git (KDE:Unstable:Frameworks and KDE:Unstable:Applications) have switched their Qt libraries from Qt 5.

As KDE software (be it the Frameworks libraries, the Plasma 5 workspace, or the Applications) develops during a normal release cycle, a lot of things happen. New and exciting features emerge, bugs get fixed, and the software becomes better and more useful than it was before. Thanks to code review and continuous integration, the code quality of KDE software has also tremendously improved. Given how things are improving, it is tempting to follow development as it happens.

A new version of Danbooru Client is now available! What is Danbooru Client? Danbooru Client is an application to access Danbooru-based image boards (Wikipedia definition). It offers a convenient, KF5 and Qt5-based GUI coupled with a QML image view to browse, view, and download images hosted in two of the most famous Danbooru boards (konachan.com and yande.re). Highglights of the new version The image window is shown again with recent Qt and KF5 versions; Remember the last directory saved when saving images; Remove (hopefully) hang when saving images.

In the past week, the KDE Community Forums administrators had been discussing how to improve the current forum layout. There are a few reasons in favor of a reorganization. First of all, to reflect better what KDE is (a community that produces software). Secondly, to provide a better organinzation for all kinds of people: those that require support, those that offer support, and those who want to contribute. All of this within a (hopefully) logical structure.

KDE has recently released the newest Release Candidate of the Applications 15.08 release. Among the new features and changes of this release, there is a technology preview of the new KF5-based KDE PIM suite (including reworked, faster Akonadi internals), new applications ported to KF5 (the most notable ones being Dolphin and Ark). After some consideration and thinking on how to allow users to test this release without affecting their setups too much, the openSUSE community KDE team is happy to bring this latest RC to openSUSE Tumbleweed and openSUSE 13.

Since [26th December 2005]({{ site.url }}/2005/12/up-and-running/), I’ve been runnning this blog with Wordpress. At the time there were little alternatives and finally I had got hold of a host (Dreamhost, at the time) that supported PHP and MySQL without being overly restrictive. 10 years later, things have somehow changed. The issue The main reason lies in how Wordpress has evolved over time: no, I’m not speaking about the subjective “bloat”, but the fact that it’s been moving towards a full-blown CMS, which is not what I have in mind to run my blog.

A lot has been happening on the KDE side of openSUSE… this post summarizes what’s been going on so far. Live media for Plasma 5 One of the most-often requested ways to test Plasma 5, given it can’t be coinstalled with the 4.x Workspace, is the availability of live images to test either in VM or bare metal without touching existing systems. Given that other distributions started doing so since a while, naturally openSUSE couldn’t stay still.

Following up on yesterday’s release, I’ve released Danbooru Client 0.3.0. This early new release is mostly due to the fact that the QML view file wasn’t installed (sorry!) so part of the UI would not even load (or even crash). That said, I’ve managed to get some extra features in: Fade-in/out animation when posts are being downloaded Support for tagging is back (EXPERIMENTAL): it is optional, and requires KFileMetaData (not yet a framework, but should be distributed with Plasma 5).

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

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.

The ever-amazing Plasma team from KDEjust put out a new release of Plasma. I won’t spend much describing how big of an improvement it is - the release announcement at KDE has all the details needed to whet your appetite. And of course, now it’s the turn of distributions to get out packages for the users at large. This is also the case for openSUSE. The KDE:Frameworks5 repository hosts the new 5.

Short version: the KDE PIM in openSUSE Tumbleweed is moving from 4.14.x to the KF5 based version. More details below. Some history As you may know, up to now the default PIM suite for Plasma 5 in openSUSE Tumbleweed was the KDE PIM 4.14, based on kdelibs 4.x. While upstream KDE has offered a KF5-based version since Applications 15.08, it has been originally marked as a technology preview, so we (the openSUSE community KDE team) thought it would be more prudent to stick with the 4.

Following up onKDE’s announcement of the latest stable release, we have now packages available for 12.3 and 13.1 (a 13.2 repository will be made available after it is out). You will find them in the KDE:Current repository. Current users of this repository will get the new release automatically once they update. Why you should upgrade? You can take a look at the list of changes to get an idea. These fixes touch many important KDE applications, including KMail, Okular and Dolphin.

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.

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.

Requests to unlock KWallet automatically on login (assuming the wallet password and user password are the same), like gnome-keyring can do, have been going on for years: in fact, bug reports requesting this feature are quite old. Recently, thanks to the efforts of Alex Fiestas, a PAM module, which interfaces KWallet to the system authentication methods, has been developed. In parallel, the necessary glue code has been also added to the various parts of the KDE workspace so that it could make use of it.

This is a guest post by Raymond “tittiatcoke” Wooninck, with contributions from myself and Hrvoje “shumski” Senjan In the next hours the [KDE:Current]({{ site.url }}/2014/03/being-current/) repository will publish the latest release from KDE (4.13). As that this release comes with a big change (the new semantic search), we would like some simple steps in order to perform the right upgrade. Before the upgrade In order to migrate data automatically from the Nepomuk store to the new format, you will need Nepomuk up and running, and just for the time needed for the migration.

It is not news that openSUSE, through to the effort of the openSUSE community KDE team, offers several third-party repositories for those who want the latest software from KDE. Since a while, stable releases were offered in the KDE:Release:4x repositories, created with every major release of KDE software. These were meant to offer the latest and greatest to the users without having them to track KDE:Distro:Factory, which is instead used to track packaging for the next openSUSE release and is more in a state of flux.

Yesterday KDE released their first beta of the upcoming 4.13 version of Workspaces, Applications and Development platform. As usual with the major releases from KDE, it’s packed with a lot of “good stuff”. Giving a list of all the improvements is daunting, however there are some key points that stand out: Searching: KDE’s next generation semantic search is a prominent feature of this release. It’s several orders of magnitude faster, much leaner on memory and generally is a great improvement from the previous situation (this writer has been testing it for the past months and he’s absolutely delighted about it).

Among the different widgets I use on my desktop, there is a small one which tells me my current public IP address. The reason I’m having it is due to the fact that my own ISP uses a NAT for almost all its customers (don’t ask - long story) and so I need to keep tabs on my current IP, because it may have been blacklisted, and so on. Up to now I was using this plasmoid written in Python, but the code had several issues and used its own way of getting the public IP.

And so, finally openSUSE 13.1 is out of the door (I couldn’t celebrate like I wanted, as I’ve been very busy). This release has lots of improvements, and of course, the latest stable software from KDE. It is time (perhaps?) to look back and see what the team has done during this development cycle. With regards to the KDE software packaging, the past 8 months have seen quite an increase in the involvement of poeple from the community.

In the past few days, the openSUSE KDE team has been working hard, following the footsteps of the nice work done by the Kubuntu and Arch Linux communities, to provide Qt5 packages for the distribution. In fact, work was already done in the past, but the packages were not coinstallable with the existing Qt4 installation. Thanks to a renewed effort, the OBS holds now Qt5 packages that won’t overwrite the existing Qt4 install: they currently live in the KDE:Qt51 repository (Factory and openSUSE 12.

The latest release of the KDE Platform, Workspaces, and Applications (4.11) is around the corner: in fact, the last RC was recently made available. We’re almost there, but it doesn’t mean that testing and reporting should stop: on the contrary, it is needed even more to ensure that no bad bugs crawl up in the final release. As part of this effort, openSUSE packages for RC2 have been released through the OBS, and are available in the KDE:Distro:Factory repository.

The latest release from KDE moved from beta to RC stage, thus finding and reporting bugs is more important that ever. At the same time, the distribution packaging teams are also working in polishing their packages. As far as openSUSE is concerned (not dissing other distros, just mentioning the one I’m involved in ;), you can kill two birds with one stone by installing the packages provided in the KDE:Distro:Factory repository.

KDE released the second beta of the KDE Platform, Workspaces and Applications 4.11, and after the necessary time for the OBS to build packages from the released tarballs, packages are available for openSUSE 12.3 and openSUSE Factory. Like the previous beta, they are available through the KDE:Distro:Factory repository. 4.11.x is is targeted for inclusion in the upcoming openSUSE 13.1. So far 4.11 has been pretty stable for me, but you should never forget these packages are for testing and bug reporting purposes: don’t use them on production systems.

As a consequence of [the recent changes in the repositories]({{ site.url }}/2013/06/upcoming-changes-to-opensuse-kde-repositories), the openSUSE KDE team is happy to announce the availability of packages containing the first beta of the KDE Platform, Workspaces and Applications 4.11. Packages are available in the KDE:Distro:Factory repository. As it is beta software, it may have not-yet-discovered bugs, and its use is recommended only if you are willing to test packaging (reporting bugs to Novell’s bugzilla) or the software (reporting bugs directly to KDE).

Since KDE has released the first beta of Platform, Workspaces, and Applications 4.11, there will be some changes in the packages offered in the openSUSE repositories. In short: KDE:Distro:Factory will now start tracking 4.11 betas and RCs: packages are being worked on. Use this version to test packages and to report bugs upstream. KDE:Release:410 has been decoupled from KDE:Distro:Factory. If you were using 4.10 packages from KDF, you’re highly encouraged to move to this repository.

These posts kind of sound like a broken record, right? ;) Anyway, since KDE has released new versions of Platform, Workspaces and Applications as part of the stable release cycle, thanks to the OBS we have packages available for openSUSE 12.2 and 12.3. The 4.10.4 update will also be released as an official update for 12.3 in due time. Where you can get the packages? Two places, as usual: KDE:Distro:Factory in case you are interested in contributing to packaging for the next openSUSE release; KDE:Release:410 (openSUSE 12.

KDE released 4.10.3 versions of the Platform, Workspaces and Applications yesterday, with more than 70 bugs being fixed. Notably: Several fixes in handling encrypted mails in KMail Fixes for KDEPIM syncing and ownCloud A number of improvements in Dolphin, including crash fixes Optimizations in the Plasma Workspaces [The full list](https://bugs.kde.org/buglist.cgi?query_format=advanced&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bugidtype=include&chfieldfrom=2013-01-01&chfieldto=Now&chfield=cf_versionfixedin&chfieldvalue=4.10.3&order=Bug Number&list_id=638034) has other important changes. As usual, there are two different repositories from which you can get them:

KDE has released its monthly update for the 4.10 release, and after a brief wait while the Open Build Service worked over the released tarballs, the openSUSE KDE team is pleased to announce the availability of the 4.10.2 release packages for openSUSE 12.2 and 12.3. []({{ site.url }}/images/2013/04/757111961.png) Despite being a minor release, more than 100 bugs were fixed, in particular there were many KDEPIM fixes touching both the low level stack and KMail/KAddressbook/Kontact.

Hot on the heels of the announcement from KDE, the openSUSE KDE team is happy to announce the availability of packages for the latest stable release of the KDE Platform, Workspaces, and Applications. Packages are available in the KDE:Distro:Factory repository (which is where the packages to land in 12.3 are tested) for openSUSE Factory (soon to be 12.3) and openSUSE 12.2 and soon (when the Open Build Systen finishes rebuilding a number of packages) in the KDE:Release:410  repository for openSUSE 12.

Following up on the announcement from KDE, the openSUSE KDE team is happy to announce the availability of 4.10 RC3 packages. Remember that they are packages meant for testing and reporting bugs, so that the next release will be as polished as possible. You will find the packages in the KDE:Distro:Factory repository. An updated live media based on the upcoming openSUSE 12.3 ([see previous post]({{ site.url }}/2013/01/test-the-upcoming-opensuse-12-3-and-kde-workspace-applications-and-platform-4-10-rc2)) is also available (files named KDE4-4.

Following up on my previous post, a different type of image has been made by the openSUSE KDE community members. In particular, alin has created images sporting the same software from KDE (4.10 RC2) but using the upcoming openSUSE 12.3 as base. Download links: 32 bit version 64 bit version Release directory (in case the above links go 404; the files are named KDE4-.4.10.RC2-Live) These images are provided not only to test 4.

The 4.10 release for the KDE Development Platform, Workspaces and Applications is drawing nigh… as you may have read, there is now an additional release candidate in order to test some last-minute changes. Of course, the KDE developers can only do so much: it’s impossible to test all possible combinations. That is, unless the community at large helps by finding and reporting issues the developers can fix. But doing so requires a 4.

Yesterday Alex Fiestas showed on his blog a video of a recent development version of the KScreen library, created to handle easily multiple monitor setups in KDE, almost in an “automagic” way. As this is a project where configurations and setups are highly heterogeneous, a lot of testing is required to ensure things work reliably. Of course, you cannot ask a developer to have all sorts of screen combinations, but remember one of the strengths of FOSS: “many eyes make bugs shallow”.

openSUSE is migrating to the use of systemd for the upcoming 12.3 version, given the difficulties that emerged in trying to co-maintain two different init systems (SysV + systemd). While I am not going into the details of this choice (I leave this to more informed people), this has some consequences for software higher in the stack. As ConsoleKit is deprecated, systemd offers its own daemon to keep track of sessions and assigned seats in a system.

The KDE community has just released Beta 2 of the upcoming 4.10 release of the Development Platform, Workspaces, and Applications. Of course, distributions are providing binary packages for the adventurous… and how could the green distro be left out? In fact, it is not. Beta 2 packages were uploaded and built in the KDE:Distro:Factory repository. Updated packages have also been submitted to the development version of openSUSE (Factory) as the ultimate goal is having 4.

When I’m not on forum duty or handling openSUSE-related contributions, I try to improve my code contributions to KDE, even though I’m by no means an experienced programmer (I program all day long in Python, but I’m still a biologist after all). For the upcoming 4.10 release I’ve been polishing up Python 3 support. As you may know, Python 3 isn’t the standard in many distributions (Arch Linux excluded), but despite the slow start, it is slowly gaining steam.

As others, bigger members in the KDE community say, “nobody will do it for you, and therefore they will”. The patch from the title comes from such a story. Let’s give some background first: I’m really a heavy activity user, especially when working. My home PC has about five activities, my work one 3, and I managed to compartimentalize the various “topics” that each activity does pretty well. After an update a couple of weeks ago from the latest code from KDE git, I started noticing weird behavior.

Recently Fedora’s Lukas Tinkl pushed to kdelibs (for the 4.10 release) a patch that enabled Solid to talk to udisks2, which is a replacement for udisks. Fedora already moved to udisks2 (and killed HAL) and future GNOME releases will only use udisks2, so the need for a working backend was a necessity, and at the same time they acted like good open source citizens, and pushed the code both to 4.

Many of you know that KDE Brainstorm ideas aren’t posted straight away: they are always pre-screened to avoid repetitions, features that cannot be implemented technically, violations of the Code of Conduct, and so on. This is possible thanks to the work of the Idea Moderators, that patrol Brainstorm and evaluate the new ideas being posted. Recently, a few of them got too busy and thus we’re experiencing a backlog of ideas staying in the Vault (the staging area for evaluation) for longer times than usual.

The recent post by Dario on the KDE Workspace Vision raised some concerns on why Brainstorm was not used.One commenter even said _Right now it feels like “Throw an idea over a wall for no-one but end users to discuss until it bitrot’s”. _ _ _ The Brainstorm section is indeed in need of help. To make it more useful, a couple of things are needed: Statistics to evaluate which ideas are best representative: it can’t be just the number of votes per se as there are things like confirmation bias or controversies that may inflate the numbers Integration with Bugzilla: a way to automatically (using XML-RPC) send the ideas flagged as representative to a bug report filed under “wishlist”.

Recently we’ve seen several blog posts on Planet KDE related to Nepomuk. Reading those I thought that I could add some (little) semantic features to [Danbooru Client]({{ site.url }}/projects/danbooru-client). Danbooru Client already makes use of Nepomuk: if enabled, tags extracted from Danbooru items are added as Nepomuk tags. But since at least some Danbooru boards are specialized in certain types of images (e.g., wallpapers only, for examples) I found it would be nice to have Nepomuk show me only the images that come from a specific Danbooru board.

Recently in the Plasma mailing list, KDE developers have discussed a new screen-locking implementation that could be added to the upcoming 4.8 release of the KDE Workspaces. The first reason to do so was to solve some security constraints of the existing implementation. As an added bonus, screen locking should be also more aestetically pleasing. There is however a trade-off: such implementation would mean that screensavers that rely on X (also called X screensavers) would not be compatible.

In one of my previous blog posts I dealt with [tagging files and resources with Nepomuk]({{ site.url }}/2010/10/pykde4-tag-and-annotate-files-using-nepomuk). But Nepomuk is not only about storing metadata, it is also about retrieving and _interrogating _data. Normally, this would mean querying the metadata database directly, using queries written in SPARQL. But this is not intuitive, can be inefficient (if you do things the wrong way) and error prone (oops, I messed up a parameter!

Recently, a question came up on the KDE Community Forums regarding the use of multiple Google Calendars with KOrganizer. The preferred access up to now has been with googledata Akonadi resource, however that doesn’t support more than one calendar, and (at least from my unscientific observation) seems to be rather unmaintained these days.

Luckily, not all’s lost. Akonadi recently gained the opportunity of accessing CalDAV resources, and Google Calendar also offers a CalDAV interface, hence this is possible.

This post will briefly describe how (thanks go to PIMster krop, which casually mentioned the possibility on IRC and prompted me to investigate).

Some of the oldest readers of this blog are well aware of [a certain hobby of mine]({{ site.url }}/category/anime). Over the years I’ve always wanted to write more about that, including the stuff I’m viewing nowadays, but I found a hassle to collect snapshots from videos / DVDs, selecting them, and so on. Recently I learnt that VLC has some rather complete Python bindings, and I thought, why not make the process automated?

As you may already know, recently the KDE sysadmins completely overhauled the commit hooks used with the Git infrastructure. Written in Python, they have already brought significant improvements to the current workflows. These hooks include keywords that when specified trigger particular actions: the most used are to CC specific email addresses (CCMAIL), to CC bug reports (CCBUG) or to close bug reports (BUG). With the adoption of Review Board to facilitate code reviews, there were also requests for a REVIEW keyword that could close the review requests without asking the submitters to do so manually (which is slow and not always effective).

One of the greatest strengths of KDE is undoubtedly the asynchronous and network-transparent I/O access, employed by the so-called “I/O” slaves, part of the KIO class. If you are developing an application that requires file or network access, those classes make things incredibly simple to do, and they don’t freeze your GUI when you are in the middle of a process. In this post I’ll show how to use KIO to retrieve files from network resources using PyKDE4.

Some time has passed since I last blogged… this was not only due to lack of time but also due to motivation (writing long texts can be discouraging at times). In any case, I’d like to rectify for that. In this post, I’ll talk about Nepomuk, and in particular how to use it to tag and annotate arbitrary files using its API in PyKDE4. Before starting, let me say that creating this tutorial was only possible thanks to the help of Sebastian Trueg, who helped me by pointing out some mistakes I was doing.

The rest is up to you to figure out.

With my last entry, I announced the start of the work for an OCS library for the KDE Community Forums. Today I’d like to blog again about the recent developments. First of all, now there isn’t one, but two Python modules: _ocslib, _ a pure Python module that can be used to interface with OCS-based forum systems; ocslibkde, a PyKDE4 based module that can be used to interface with OCS-based forum system in KDE applications.

For KDE developers, web-based forums are often uncommon workflows. Indeed, for communication among developers mailing lists are much better tools, especially since you can handle everything inside a client (most of the time), compared to forums where you have to use a web browser. The ways of reading, replying and interacting with posters are dramatically different. And that is why some developers find themselves uncomfortable with the KDE Community Forums.

In the past weeks and days, the KDE Community Forums staff has been working to bring new features to improve even more the user experience. A few months ago, the staff was discussing the idea of finding a way to guide users to the most appropriate forum to post their questions or discussions. Now, thanks also to the return in service of one of our admins (welcome back, sayakb!) the feature is now being implemented, as the screenshots below will show.

 My Akademy talk proposal was not accepted, but the organizers were kind enough to offer me the chance to hold a BoF on the same subject. Now I bet you wonder on what I’m going to discuss, and I think the title already gives you an idea: KDE and bioinformatics: the missing link Although in the KDE community we have our fair share of scientists (hey there, Stuart!

Those who use PyQt and PyKDE4 are certainly familiar with the syntax used to connect signals and slots: [python] from PyQt4 import QtCore from PyQt4 import QtGui from PyKDE4 import kdeui class MyGUI(QtGui.QWidget): def __init__(self, parent=None): super(MyGUI, self).__init__(parent) self.pushbutton = kdeui.KPushButton() self.pushbutton.setText("Push me!") QObject.connect(self.pushbutton, QtCore.SIGNAL("clicked()"), self.button_pushed) def button_pushed(self): print "Button clicked" [/python] The main advantage of this syntax is that it’s very close to the C++ equivalent, and so you can translate easily from C++ to Python.

Recently, I investigated how to perform some checks on web addresses using KIO for Danbooru Client. My old code was synchronous, so it blocked the application while checking, thus causing all sort of troubles (UI freezing, etc.). Therefore, making the switch to KIO was the best solution. However, I had one problem: how could I check the HTTP response? I knew already that the various ioslaves can store metadata, consisting of key-value pairs which are specific on the slave used.

With my brand-new SVN account, I just committed some code to kdeexamples, KDE’s example code module. In particular, I committed a simple example which shows how to use KConfigXT via PyKDE4, a simplified version of [what I wrote about here]({{ site.url }}/2009/10/howto-kconfigxt-with-pykde4). As most of KDE is C++, and the Python API docs are translated directly from the C++ API docs, it is essential to have good examples to help newcomers learn faster.

Sometimes answering apparently harmless questions on instant messaging can have unexpected results. In particular, I was telling about Danbooru Client to someone and a question popped up “Why don’t you support pages?”. It seemed a nice idea, so I branched off the code (yay for git!) and started working on it. Well, it took me more than a month to get this thing done… I didn’t spend every day coding, but it was a challenge.

KDE SC 4.4 Beta 1 has been released, and of course I couldn’t stay still. Thanks to the friendly openSUSE Build Service, there were packages available, so I just pointed my zypper sources to KDE:KDE4:UNSTABLE:Desktop repository, adjusted a few other things (mainly other third-party repositories) and updated.

Do you like KDE? Did you ever find yourself in a position of wanting to help, but you didn’t know what to do, or who to talk to? Do you feel you could use help to get started? Today, the KDE Community Forums would like to provide the opportunity to answer those questions by annoucing the continuation of the tutorial courses known as Klassrooms. What are Klassrooms? Klassrooms are tutorial “lessons” held in a specific area of the forum.

Well, there wasn’t a Day 1 for me (I got to the hotel too late to follow the first day of the meeting), so that is why I’m starting on day 2. To start, I need to say that I had never been to a sprint before: I am already accustomed to meeting for real someone from online, but for all the attendants, they had been just names or nicks on IRC.

A while ago I presented [“danbooru2nepomuk”]({{ site.url }}/2009/10/danbooru2nepomuk-a-nepomuk-tagger-for-danbooru-images), a small program to tag images coming from Danbooru-based image boards. Today I want to present the evolution of that program, that is a PyKDE4 client for those boards.

If you read around the KDE Techbase, or if you develop KDE applications, you may have heard about KDE’s KConfigXT. This is an extension of KDE’s KConfig, and can be used to generate nice configure dialogs with multiple pages with minimal effort, also taking care of saving and applying settings. In short, something really neat! But there are problems when using it with interpreted language bindings (such as PyKDE, which is the one I use):

• KConfigXT requires an XML file and an INI-like file to be compiled by kconfig_compiler in order to produce C++ files
• There is no such a tool (at least to my knowledge) that does the same job for bindings

So what to do? Either give up on the niceness of KConfigXT, or work around the issue. I chose the latter.

In line with the project’s committment to openness, the KDE developers and contributors are not a secretive bunch. In fact, the “People Behind KDE” initiative has provided the community with interviews of quite a number of the developers. And by reading those interviews, haven’t you ever felt the need of asking a specific question, outside from those prepared by the interviewer? For example, more details about what the specific developer is doing, or what his/her plans are for the next version of KDE.

While browsing around kde-look.org, I’ve stumbled upon a nice little Plasma scripted widget, and I’m publishing this to have it get more exposure. A good part of the KDE community knows at least little about Nepomuk, and its ability to attach semantic tags to your files - basically words that describe the file, be it an image, a text document, or anything you’d like. For example, you could tag all the photos from your vacation with the name of the place you’ve been.

Hello people! Yes, it’s been a while but I haven’t forgotten about it… with the Brainstorm’s new look and most technical issues resolved, I’m able to make Brainstorm Digests more often (hopefully!) Issue 3 - Special summary issue Since we have skipped a few months, what I’d like to present today (aside the usual data about the past month), is a general overview of the state of Brainstorm since the start of the initiative a while ago.

As you all know, KDE 4.3.0 has been releeased today! Now it’s the time to tell the developers “thanks” for their hard work. Join us in the KDE Community Forums and spread the word!

Up to now, the main language in which KDE applications are developed is C++. This is a perfectly valid choice: however, at least for users that don’t have a computing background (I include myself in the list: I do science) C++ can be a rather steep requirement (although Hans, fellow staff member at the KDE Community forums, is doing a nice job in explaining his learning experience). Scripted language bindings (that have a lower barrier of entry) for KDE exist: on top of my memory I can list Python, Ruby, and C# (and I’ve probably missed a few).

The KDE Brainstorm, where users can post and vote for feature requests for KDE, is the most visited area of the KDE Community Forums. In an effort to improve the experience of both users and developers, the KDE Community Forums staff is proud to present a brand new version of the KDE Brainstorm.  The new interface resembles the IdeaTorrent sites, but it is still powered by the forum software (phpBB), a clear example of the flexibility of the platform.

A few may know that I more or less maintain the Plasma FAQ page on KDE’s UserBase. Given the rapid advance of Plasma between KDE versions, each time a new version is out a new FAQ needs to be made, as the content rapidly becomes obsolete. For 4.3, unfortunately, I’m not sure I’ll be able to put a new version up in time for the 4.3 release. The reason is mostly practical: it takes a bit of work to collect and add information, and currently my free time is limited due to a rather heavy workload and some other commitments.

Today, a major upgrade of the KDE Community Forums took place. The change brings quite a number of changes to the forums themselves, and it’s a further step towards providing a better experience for KDE users (and developers too!).

Hello, and welcome to the second issue of the KDE Brainstorm Digest! This issue comes in slightly late, due to some real time commitments, but I couldn’t leave you without it, could I?

A rather big change has gone into KDE’s SVN recently: Ben Cooksley (bcooksley) and Mathias Soeken (msoeken) have committed a complete rework of System Settings.

Compared to the previous implementation, System Settings now has two operational modes, one being the current icon-based view since KDE 4 (and also seen in Kubuntu prior to KDE 4), and a second view, named “Classic”, which reimplements the old KControl look and feel. The latter change is probably very welcome to anyone who found System Settings less useful than the old KControl. The current view used can be changed in the configuration options. In addition, upon hovering an icon or module that show if there are any sub-modules associated.

Currently, the openSUSE Build Service contains Amarok 2.1 beta packages only for the KDE:KDE4:UNSTABLE repository (i.e. current trunk, soon-to-be 4.3). However, a quick search identified a repository that contains a RPM of current 2.0.90 compiled for the KDE:KDE4:Factory Desktop (which will change to 4.3 with Beta 1) andanother one for the KDE:42 repository. So you can add them using YaST or zypper and download the relevant package. I had to force a repository using zypper, otherwise zypper would complain and try to install amarok 1.

Hello, and welcome to the first “issue” of the KDE Brainstorm monthly digest. First of all, a few words of introduction. There are quite a number of ideas being posted on the KDE Brainstorm, and it would be nice to know how the initiative is faring, and important highlights, like what ideas are more popular, which are more controversial, etc. That is why the idea of a monthly digest was born (in a similar fashion as the fabolous Commit Digest).

Via Harald Hvaal’s blog I learnt that the first non-forum suggestion has been implemented! I think this shows without doubt that initiatives like the KDE Brainstorm are undoubtedly useful to the community at large, both users and developers. Keep on rocking!

In the past months I’ve always wanted to write a small Plasma applet to aid me in some boring tasks as a bioinformatician. One example (for the non-scientific crowd out there) is when I find a specific gene out of my analysis work which I want to take a look at. I am often lazy, so instead of firing up the browser to look at the online resources, I wanted to write something which could access said resources programmatically.

Now that the KDE Brainstorm has been launched, it’s time to take a look at the results so far. Currently, the forum hosts 160 threads, approximately one for each idea, and 441 posts. Not bad for the first two days of operation. At the same time, the staff has been working hard to make sure only appropriate ideas (not bug reports, not duplicates…) are on the forum. People have also begun voting, although slowly: it’s understandable, given the fact that there are so many threads in so little time.

It’s finally there: KDE Brainstorm has been launched today! Like this, it will be possible to propose features and have them voted by the community, and then submit the most voted requests to the developers. Every feature request is screened prior to posting, so duplicates, spam and flames are unlikely to occur. There is no guarantee that the voted upon features will be implemented, but as opposed to individual postings, this approach reduces the noise a lot, and allows a better communication between the “two worlds” (users and developers).

No, it’s not_ _a teen-like “I hate my life, I’m going to die tomorrow” post. I’m actually referring to the comments of a person nicknamed “I Love” that are popping up in almost all blogs that are linked to PlanetKDE which deal with Plasma or KDE4 adoption. The name “I Love” contrasts with an attitude that is unconstructive and rather trollish. This wouldn’t be such a big problem, if not for the fact that posts from said individual have had a rather negative effect: for example Aaron was forced to turn comment moderation on on his blog, Jos’ entry on the new Plasma in the upcoming KDE 4.

Mtux, of choqok fame, along with another person, has written Bilbo Blogger, a blogging utility for Blogger or any blog that supports Blogger1.0, MetaWeblog, and MovableType APIs (EDIT: also GData). It is based on the KDE4 libraries and it includes a WYSIWYG editor, an HTML editor, and a Post Preview function that can even fetch your blog’s CSS to render the entry and see how it looks. It’s not released yet, but for the daring, you can actually try and compile it.

During the course of my research work, I may obtain results that are worthy of publication in scientific journals. Since my master’s thesis I’ve been using LaTeX as my writing platform, mainly because I can concentrate on content rather than presentation (I find it useful also for writing non-scientific stuff as well). Also, I can handle bibliography (essential for a scientific publication) very well without using expensive proprietary applications (such as Endnote).

In my early days I used kLyX first, then LyX, but I found the platform to be too limited for my tastes, and also LaTeX errors were difficult to diagnose. I needed a proper editor, and that’s when I heard of kile, a KDE front-end for LaTeX. Kile is currently at version 2.0.2 and is a KDE 3 application. However, in KDE SVN work is ongoing to produce a KDE4 version (2.1) and that’s what I’ll look at in this entry.

I try to use FOSS extensively for my scientific work. In fact, when possible, I use only FOSS tools. Among these there is the R programming language. It’s a Free implementation of the S-plus language, and it’s mainly aimed at statistics and mathematics. As the people who read my scientific posts know, I don’t like R much. But sometimes it’s the only alternative.

Well, what does R have to do with KDE? With this post I’d like to start a series (hopefully) of articles that deals with KDE programs used for scientific purposes. In this particular entry, I’ll focus on rkward, a GUI front-end for R.

I have been thinking of doing another Kourse at the KDE Forums, similar to the one that has produced three nice screencasts. My idea would be to show very brief and focused screencasts, a sort of “how do I…”. I have a few ideas, but I’d like to ask the KDE community at large. I’m mostly interested in showing single features (short videos), preferably of the “eye-opener” kind. If you have any suggestions, leave a comment.

Yes, I know I’m a bit late to the party (unfortunately today was one of the busiest days ever where I work), but I thought I’d join the other members of the KDE community, because KDE 4.2 has been released today. Take a look at the visual guide, or see if your distribution has already packages for you. For your enquiries, the KDE Forums are at your disposal.

If everything has gone correctly, my blog should be on PlanetKDE now. That means it’s time for an introduction for those readers. My name is Luca Beltrame, I’m a biotechnologist doing bioinformatics in the life sciences areas, and I’m a Free Software user/enthusiast since many years. I’ve been using KDE since 1.0 or so (if memory serves me well), but only recently, with the 4.x line of development, I’ve been trying to actually contribute a bit back to the project.

I just finished writing a new Python tutorial on KDE’s Techbase. This one deals with writing DataEngines in Python (a complement to Simon Edwards’s own Using DataEngines). Let me know what you think. As it’s a wiki, comments and suggestions are welcome.

It turned out I forgot to add the last screencast produced by the students of Kourse 2, so I’ll fix my mistake right now. Here’s Panel settings, by Kourse student TeaAge: [blip.tv ?posts_id=1653914&dest=-1]

Students from Kourse 2 fengshaun and Primoz have prepared two nice screencasts, dealing with the Zooming User Interface (ZUI) and desktop settings respectively. Without further ado, here they are: Zooming User Interface by fengshaun [blip.tv ?posts_id=1648944&dest=-1] Desktop settings by Primoz [blip.tv ?posts_id=1646835&dest=-1] As usual, both Free and non-Free versions are available. The students are also at work on subtitled versions, without the Notes plasmoid. I’ll be sure to post them once they’re done.

As some people already know,I’m mentoring a group of students on KDE Forum to create Plasma screencasts (from the upcoming KDE 4.2 version). After several adjustments back and forth, the first one (made by kourse student Primoz), showing off the various desktop settings, is complete. This version uses the Notes plasmoid to keep track of annotation, but we’re also evaluating subtitle-based versions. In the mean time, enjoy! (and spread the word).

Today I was adjusting a bit the layouts of the Activities (as defined in Plasma) to better suit my workflows. To do so I was using the brand new Activity Bar which is present in KDE 4.2. It’s very neat, but takes up space on the desktop, and while it’s not a big deal on my main PC (1280x1024 resolution), it is an issue on my recently-resuscitated EeePC (1024x600). It was then that it occured to me that such applets are, in Plasma-speak, PopupApplets, which means they adjust their behavior depending if they are in a panel or “free”.

Today I’m in a posting spree…This clip shows how to resize and move Plasma panels around. [youtube]http://www.youtube.com/watch?v=Rmpv-S5JJI4[/youtube]

Following up on my previous post, here is another screencast showing off how to create a sidebar panel and add a few plasmoids to it. As usual, the version on Youtube has annotations. [youtube]http://www.youtube.com/watch?v=WPeFSDdt2PY[/youtube]

I’ve put together a small video that shows what you can do with zooming in and out with Plasma’s Zooming User Interface (ZUI). Enjoy. (note: the version on Youtube has also annotations that explain better what is going on) [youtube]http://www.youtube.com/watch?v=EhODrJkoidA[/youtube] If you can, please spread the link to the video. We need more correct information out there.

Those of you that follow my Linux-related posts know that I work (along with others) on a FAQ trying to explain some magic behind KDE 4.x’s Plasma. Now, especially since on the Internet, there is the need to spread correct information (most of the naysayers are not quite informed). So, if you want to help KDE, please spread the word on the Plasma FAQ! If people have questions on Plasma, just direct them to

Now even the (once respected) Steven J. Vaughan-Nichols is jumping on the bandwagon of Plasma haters. With a rather uninformed and rant-ish entry that just advocates a fork, like some other people said on the kde-devel mailinglist a week or two ago. The entry is rather dismissive of everything in KDE 4 save Plasma (and a mention on Dolphin’s single click icon), and also gets some facts and links wrong (yes, the Plasma web site is outdated, but since the developers are busy coding, someone else should step up and help).