GSoC – The End

What We Have Done

So, Google Summer of Code has ended (more than a month ago, but I haven’t managed to write a wrap-up post since). It’s been great. Challenging though, but a nice and useful experience.

First of all, we have managed to have a usable and relevant GUI framework for handling searching of Nepomuk resources as well as displaying and editing them in either a generic or a customized way. As described in an earlier post, I wrote components such as a list widget for Nepomuk resources with its appropriate model and delegate, an editor to handle resources and their important properties using a plugin system (editing plugins are used based on the resource type), a flexible widget for editing single Nepomuk properties and other GUI elements.

Sebastian and I also implemented a flexible framework for faceted searching using Nepomuk search terms. (This has been changed since by Sebastian, switching to a revamped version of the old faceting approach used by Alessandro Silvieri, but I haven’t been able to check that out yet.)

Finally, the search GUI application built upon the API features a query editor, a facet widget and the list widget which provides the editing widgets for relevant displaying and editing of resources.

Details

Not to flood the post with screenshots, I’m showing three relevant usage scenarios:

Example 1: The Result List

Simple searching based on two tags (latex and thesis) from the facets widget. It shows all resources having those two tags.

Notice that the label, description (grey text with italics, where applicable),  and resource type are displayed in the list for each item (icons are also displayed, but none of the items have them in this example)

Also, the available (but not shown) context menu actions on the items are Copy Label, Copy URI and Delete Resource.

Example 2: Displaying an Item

An item is expanded and displays relevant details, such as rating, tags or creation date.

When an item is expanded, it can be modified by either double-clicking on a value or by enabling editing mode for all the properties.

A resource can be saved or the values can be reverted.

Notice also the Actions menu which lists the available actions defined on a resource, such as the default Show Related Resources, or the custom-defined Reply to Email and Forward Email for Email resources.

Example 3: Editing a Property

Editing the hasTag property

Each value type has its own editor defined, such as a spinner for an int or a KDateTimePicker for a DateTime value, or a ResourceCreateAndSearchWidget for Resource values, etc.. If a user double clicks on a value, its editor is displayed.

In this case, the hasTag property can have multiple Resource objects, so you can see a widget for each of the tags (latex, work, thesis, testtag) and a + button at the bottom for adding a new resource.  Each widget allows for 1.) opening the corresponding resource for a more detailed examination, 2.) replacing the current one by creating a new one or searching for a resource of the give type, and 3.) removing it.

The End

Since GSoC ended, I haven’t been able to work on it at all because of two summer camps I’ve co-organized (a children’s camp and a youth camp, trying to present Christ’s love and forgiveness of sins and a blessed life in Him) and the time-consuming job-hunt I’ve been doing (writing the CV, looking for companies, writing cover letters, studying for a technical interview).

Sebastian has done a lot of work since, revamping the facet framework, preparing it all for Dolphin integration and for moving it to kdelibs. This is awesome and I’m really looking forward to see the end result.

Finally, I want to thank Sebastian for the great mentoring he’s done, also Evgeny for all the useful advices and assistance. It was nice to work with Artem and Vishesh who had nice ideas and occasional bug reports. The Nepomuk and KDE community in general were of big help as well. Of Course, gratitude go to Google for this great opportunity of being financially supported in working on an open-source project.

As for me, I’m not sure what the future holds. I would’ve been nice to continue to be involved with the project and with Nepomuk in general, but if I’ll start to work (and commute 54 km daily), I’m not sure I can pledge for that. It’s been a great 2.5 years, even if mostly just using it as a programmer, I always felt being part of KDE and Nepomuk.

Advertisements

0 Responses to “GSoC – The End”



  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s





%d bloggers like this: