NEPOMUK AUDIO SEARCH

This is something I showcased at my talk in conf.kde.in. I coded it in a couple of hours. It is a lot of fun to play around with! I can’t wait to index all my videos this way. youtube d41bmTSogA4 Impressive? :D This was showcased at the beginning of the Nepomuk talk under the section “Nepomuk is not about searching, but here are some cool things that it can do!”

CONF.KDE.IN IS GOING TO ROCK!

I’m going to state the most utterly insane thing I can think of – “You have not heard about conf.kde.in!“. I know, I’m crazy! But just in case you haven’t – conf.kde.in is the first Indian KDE Conference to be held in Bengalurufrom the 9th – 13th March. We have a spectacular list of talksabout topics ranging from Localization to Packaging to hard core coding! Additionally we have a series of workshops planned to get you started with KDE, and, help, you discover the amazing KDE community.

NEPOMUK BACKUP

Roughly 2 weeks ago, just before the feature freeze, the Nepomuk backupsync service was pushed into the trunk. A long time ago I posted a lot of features about the ‘planned’ Nepomuk Backup service. I did land up implementing most of those features, but ultimately disabled some of them for a more stable backup experience. I thought it would be better to have a stable backup tool, without all the frills, compared to unstable tool which may potentially mess up your data.

NEPOMUK: BACKUP & SYNC

How time flies.. a month of the official coding period is already over, and I’m nowhere even close to saying that this part works perfectly. Most of my code is still in the requires exhaustive testing stages, but I can say that the core parts have been implemented. In case you’ve forgotten, or didn’t read the title, I’m implementing Metadata Backup & Sync. Well I’m supposed to be implementing sharing as well, but ignore that for now.

QT : QMULTIHASH AND QHASHITERATOR

Qt’s implementation of QMultiHash iterator is a little non-intuitive. One would expect a multi hash to be implemented as <uniqueKey, list of values> pairs, where the list of values could even be a set. But QMultiHash is derived from QHash, and it stores the same key multiple times. It stores a number of unique key, value pairs. This can cause some amount of confusion while iterating over a multi-hash with a QHashIterator.

FORWARD DECLARATION WOES

I’m ashamed to admit it, but I’ve never really understood forward declaration in C++. I know it’s used to speed up compile times, and it helps me fix cyclic dependency issues, but I’ve never really understood it. To this date, my approach of forward declaration has been - “Forward declare most of the things, and then include header files to fix compiler warnings.” I know that’s not the best approach, and I should have read about it earlier, but …

NEPOMUK GSOCER'S PROJECT INTRODUCTION

Is GSoCer even a word? It seems like a Gnome version of soccer :-/ Well, this is my first post to the Planet, and I suppose an Introduction is warranted. My name is Vishesh Handa, and I’m currently in my second year of B.Tech in Computer Science at Galgotia’s College of Engineering, India. I’ll be officially working on Nepomuk during the summer. (Yaye!) My project is labeled Metadata backup, sync and sharing.

GOOGLE SUMMER OF CODE 2010

I GOT IN!! Link!Hurray!!

GOT A KDE SVN ACCOUNT

Before I say anything else, scream with me - “Wooo Hooo”, “Yippee”. You didn’t scream, did you? :-( Anyway, I’m officially allowed to commit my changes now! Yaye! :-D

FIRST KDE CONTRIBUTION

Okay! So, I haven’t been posting at all. I know, I know! :-( BUT, I made my first actual contribution to KDE a couple of days back! Hurray! :-D The last time I tried to fix a bug, it never really got accepted or rejected. The developer of KSnapshot never returned my emails, even after I pointed out that it was my first patch. This really dissuaded by from contributing to KSnapshot, and even though I knew how to fix other bugs, I never actually got down to doing it.