The Nepomuk development process has been fairly closed to outsiders. This was never a conscious decision made by the Nepomuk Team, we just never took the effort to open up the development, and make it more appealing to new comers. For most of the last 2 years, the development model has been Sebastian and I working on our own personal list of things, and occasionally sending private emails to each other or communicating via IRC.
In case you haven’t been running trunk, or haven’t tried out the latest release candidates (you really should), you should know that dolphin has had a lot of major improvements since the last release. One of the features I really love is better Nepomuk integration. This enhanced user visibility lands up exposing bottlenecks, and performance problems. That’s exactly what happened with the nepomuk search kio slave. Dolphin exposes this neat sidebar which allows users to list out the different kind of files - Documents, Images, Audio and Videos.
For those of you who don’t know, I’m currently at Tallinn, Estonia for Akademy 2012. Here at Akademy, yesterday was an amazing day for Nepomuk. Early morning we had a Nepomuk BOF titled ‘Constructive Criticism - Prioritizing Nepomuk development’, and it was really good. I wasn’t sure if I shouldn’t have named it such, cause that might have ended in people just coming and complaining, but surprisingly everyone was really nice and constructive.
The Nepomuk team has been working really hard to fix the problems with virtuoso consuming too much memory and often just going bat crazy. And now finally we’ve figured it out. It wasn’t the obvious solution, but we think it’s going to work out very well. From now on virtuoso won’t be shown in ksysguard. Since we won’t be able to see virtuoso using up our memory and CPU, it obviously won’t be doing it.
Back in October 2010, I was trying to write automated tests for Nepomuk Backup. That turned out to be a huge disaster, but the test suite was still had some pretty good stuff in it. Most of it was based on George Goldberg’s Telepathy Test Lib. Over the last month, I’ve finally moved it to git, cleaned it up and started using it for real tests. Why do we need a testing framework?
I land up using wget a lot. I know there are better alternatives, but wget’s simplicity has won me over. Plus, with applications like firefox, I’m not always sure I’ll be able to continue the download. That’s important when I’m downloading big files, but for small files, it really doesn’t matter. A couple of days back, Martin and I were chatting about storing the metadata of a downloaded file in Nepomuk.
I meant to release a new version of Notably on Friday, but I got sidetracked with some stuff. Plus, I’ve been spending a lot of time on designing the UI for this release, which I think isn’t a good idea. Notably is still not quite mature, and I think right now features are more important than polish. Last week, I showcased some tagging UIs. They aren’t yet ready to be deployed in KDE, as they need to be polished quite a bit.
There have been cases of virtuoso going a little crazy and consuming a lot of CPU cycles. It’s extremely frustrating. However, it’s ever more annoying when you have no idea what’s wrong. Most of bug reports we get just say that virtuoso is consuming too much CPU, and that isn’t the least bit helpful. So, here is a short guide to figure out what query is causing virtuoso to go crazy.
A long long time ago, a very simple tagging widget was implemented. We always though - “Eh! This is temporary. We’ll come up with a better one later.” But that never happened. There is a lot of code in Nepomuk. However most of it is backend stuff which does absolutely marvelous things behind the scenes - Auto duplicate merging, type checking with respect to the ontologies, caching and lots more. We, however, lack good UIs.
Welcome to Nepomuk Tag Week! Well, not really, since it’s not an official thing. I’ve just been working a lot with tags lately, and this week I’m going to be spamming you with some tag related updates (One for every day of the week, minus Monday) I thought I’ll start with something small - Tag Management. We’ve been badly needing a UI to allow the users to modify, merge and delete their tags.