Although last year I also attended GUADEC, this year was like a first time to me as last year’s GUADEC was co-located with aKademy forming Gran Canaria Desktop summit and it felt different.

What do I think of this year’s? Javascript, web, introspection and shell, that’s what I think.
This is GNOME’s new route, making desktop development more webbish and it is seems like a smart one too. Now, I don’t really fall for Javascript, I think it’s ugly and not really the best choice (imho) for large projects but anyway that’s the beauty of GObject Introspection, in the future it should be easy to use whatever language one prefers.

As for the talks, I really enjoyed Luis Villa’s keynote. Xan and Fernando did a great job getting the tragedy that some times the Foundation’s mailing list is and turning it into a comedy.
Iago gave a good talk about Grilo and Juan complemented it in a lightning talk about the plugins we did using Rygel-grilo.

This year I gave again a lightening talk, this time about the Predictor Input Method which you might one day use in a mobile device or on the desktop itself if you need assisted typing. There must be a GUADEC’s rule saying that the laptop where people present the lightening talks must be a crappy netbook that takes 2 seconds before it changes a slide…

For an overall feeling of GUADEC, you can check out Victor’s post covering GUADEC, I agree totally with him.

I could also meet and chat with nice people like Eitan Isaacson, Patricia and others.

So let’s see how the projects presented in GUADEC evolve and wait GUADEC 2011 in Berlin.

And what this week? This week I’m on vacation doing an InterRail across a bunch of European countries together with my girlfriend. I visited Paris already, where I found out my french is good enough for basic stuff. Today we’re in Brussels, it’s my third time here but the first one as a turist. I’m sure the beers will taste as marvellous as always.

I’m also doing a new thing: travelling without my laptop, the N900 seems to be a perfect replacement, I (still?) love this gadget and it surelly spares some space in my backpack.

See you in some European city, I’m likely to be wearing a GNOME/Linux/Metal t-shirt… what else is new…?

These features I’m talking about fall mainly in 2 areas: improving the a11y of the UI and improving the recognition of documents.

A11y Improvement

The improvement of the a11y has the typical UI changes to include mnemonics, missing labels and relations, but also other approaches that have more to do with UX like using a progress dialog to inform users that time-taking operations are being carried. This means that now, the PDF importation and OCR won’t block the UI.
Other changes in this category were the navigation through the content boxes (before, these could only be selected by clicking on them), the selection of all boxes and the deletion of selected boxes.

The following screenshot shows the box editor area of OCRFeeder with its mnemonics highlighted:

Box edition area

Recognition Improvements

Sometimes, text columns are so close to each other that they end up being recognized as a single paragraph, so I added a post-detection method to solve this issue. This feature is optional and can be toggled from the Preferences dialog.

Here’s an example of the difference it makes:

Before columns' detection improvements

After columns' detection improvements

Scanned document images are usually skewed and this makes it more difficult for the contents to be successfully detected and “OCRed”. I decided to implement an algorithm to deskew these images. The algorithm uses the Hough transform to try to find lines in the image and their angles and, while it is a bit slow, it works well:

Skewed image

Deskewed image

This action can be used in a loaded image but can also be configured to be automatically performed before the images are added. The Unpaper tool can now also be set to be clean images before adding them.
This makes it much easier to successfully recognize images obtained from a scanner device.

Some fine tunning of the content boxes’ bounds was done by trying to shorten their margins, that is, lowering the distance between the boxes and their actual contents.

The font size recognition was also tweaked to solve the problem of having paragraphs with initials (you know, the huge starting characters) which were influencing the whole paragraphs’ font size.

To finish the recognition’s improvements, I have added an optional action to find and fix the text’s line breaks. Usually, OCR engines don’t consider “semantic line-breaks”, that is, OCR engines always insert a newline in the end of each line.
Using some regular expressions, I try to find these “fake” line-breaks and recover the original flow of the text. Like some of the features mentioned above, this one can also be turned on/off from the Preferences dialog.

Here’s how the Preferences dialog looks like now:

To finish, images can now be dragged and dropped onto the pages’ area and the mouse wheel can be used to scroll horizontally combining it with the Shift key, thanks to Stefan Löffler, and of course, several bugs were corrected and code was improved.

As you see, this is a “rich” new version of OCRFeeder that keeps being the easiest way to use OCR in a desktop. You are welcome to file bugs in bugzilla or to send patches and features’ requests to its mailing list or approaching me if you’re in GUADEC.

Download: OCRFeeder 0.7 tarball on GNOME FTP

Between hacking on OCRFeeder (expect a new version soon), giving a talk about it, attending nice presentations and chatting with people, I had a great time.
Diego’s presentation about Epiphany was simply epic and Mario gave a very complete crash course of git.

I guess there’s a first time for these things but Thursday, while I was giving a demo of the new OCRFeeder’s features, it crashed on me… Never again will I laugh at Mr. Gates and friends when their products freeze out of the blue (nah, it is too funny).
Now that I think of it… was this the first time a Portuguese man gave a talk at GUADEC Hispana?

The presentation was a cut-down version of the one I gave at FOSDEM this year and you can check its slides below (it’s in Spanish):

(thanks to Manuel Rego for reviewing my Spanish in the slides)

Here’s the group photo of the GUADEC ES attendants:

And from next Monday on, I’ll be in Den Haag for GUADEC 2010. My lightening talk about the Predictor Input Method got accepted, so if you’re into this kind of stuff, I hope to see you there.

My fellow Igalians Iago, Alejandro Piñeiro and José Dapena will give talks about Grilo, Cally and Modest 4, respectively.

As for me, I’m hoping my lightening talk about Text Prediction on GNOME gets accepted.

So, as usual, if you wanna talk about GNOME, OCR, Input Methods, Grilo, Django or Free Software in general and have beer while we’re on it, come along!

Hope to see you in Den Haag.

Grilo means cricket in Galician
(CreativeCommons photo by Danforth1)

What Grilo is

Nowadays, a number of online services provide a public API for application developers to retrieve those services’ information. YouTube lets you retrieve videos’ info by browsing or searching; Jamendo lets you retrieve its music and artists’ info in a similar way; and many more offer similar options.

Although many of these services offer a RESTful API, which already makes it easy, it is up to the applications’ developers to write code to access that API, process the results (usually XML) and build their applications’ own structures with the info. An alternative way is, of course, using an already existing library, suitable for the developers’ needs, but whose API might differ from other services’ libraries

Grilo exists to solve these issues.

Grilo has a number of plugins that retrieve media information from several services. It exposes that information in a consistent API so you don’t have to learn more than one way of getting that media’s info.
Although there are more plugins for online services, there are also plugins for UPnP or for the very filesystem.

For the examples given before, searching for media in YouTube or Jamendo would be as easy as calling a method on Grilo, either choosing to search in one, both or all available media sources.

The search would result in media objects whose information (metadata keys) can be previously configured.

So, this is a very basic definition of what Grilo is: a framework that retrieves content from various services.

What Grilo is not

One thing people often expect from Grilo is for it to play content. Well, Grilo does NOT play media and that’s a planned “misfeature”.

Grilo’s main purpose is to retrieve media, or better said, media information, and to do it well.
GStreamer is already here to play media and it does a wonderful job at it. Having Grilo to be a media player as well would deviate it from its specialization which would surely make it not suitable for some use cases.

Why should you care

More and more online services are being used in many platforms with applications being developed around them. Grilo eases the development of such applications.
For a media player dedicated to play videos from YouTube and Vimeo: Grilo gets you the videos’ URLs, GStreamer plays them and voila, you can focus on other implementation details.

Examples of applications that could have they’re job done easier would be Totem, Rhythmbox and Miro. For Totem and Rhythmbox, Rygel-Grilo (Grilo’s DBUS interface) has already shown (as a proof of concept) how easy it is to provide services as YouTube, SHOUTCast, Jamendo, filesystem’s media, and more, just in a fragment of the code needed to write a dedicated plugin for each of these services.
I put also Miro as an example application because it is a video and audio player strongly intimate with the web, Grilo could only make it easy to find these videos. Plus, Grilo’s podcast plugin could also be used to manage Miro’s video channels’ subscriptions.

As a different use case, a desktop like Meego’s, which integrates, for example, social services in it, could also integrate a way to search media, without the need to use the web browser.

So, summarizing, Grilo fills a gap in the media application development infrastructure; developers that are interested in integrating multimedia content in their applications could get an important benefit from using Grilo to access that content, and that’s why we encourage you to check it out