New job

So, for those of you that don't know yet, I left INdT and joined Collabora this month.

I had been working for INdT for almost four years and decided that it was time to try new things. I would like to thank everybody on INdT for all these years and say that it was a pleasure working with all the guys there.

From now on I will be working with Telepathy Qt4 library. It's meant to be a convenience library on top of Telepathy spec. I've spent the last 2 weeks on Cambridge and had a great time there. The whole team seems really motivated to make this library rocks. It's still in its early stages, but things are progressing really fast.

If you are interest in the code, you can check it out from here.

Mamona Rocks!

So it has been some time since I have blogged as I had a long well deserved vacation. Some time before going on vacation I spend some days with the Manona guys, helping them implement keyboard support, a long missing feature in Mamona, and a quite important one :-)

Happily I found out today that the guys succedeed in adapting my code to their needs. Details is outlined in Aloiso's blog, which can be found here.

Cool work guys, Manona is rocking even more now!

Maemo Keyboard on Qt4 applications

So, it seems I really like working with Input Methods.

This time I present you the Qt4 input context plugin for Hildon Input Method. So for now all Qt4 applications can make use of the maemo keyboard.

The code is still in its initial stage, but it's working so far. You can grab it from here.

Contributions are really welcome. If you want to help, please consider looking at the FIXME list on qhildoninputcontext.cpp :).

UPDATE: Thanks to Rodarvus to point me out that qhildoninputmethod.cpp didn't exist, changing to qhildoninputcontext.cpp :D

iPhone like keyboard on Canola

So after creating the framework to allow different input methods for Ecore and added Maemo Keyboard support for it, I decided to try a fancier thing.

It took me a few hours to get the amazing work done by Gustavo, port it to C and create an Ecore Input Method for it.

You can see the result on this video:

I would like to clarify that this video is just to demonstrate how easy is to create your own input method for Ecore. It doesn't mean that Canola will use it.

So that's it, I hope you enjoy.

If you are interested you can download the code from here.

Maemo Keyboard on Ecore applications

Last week, we at the office were discussing how we should integrate the maemo keyboard with the new Canola. After some time studying how Input Methods work, I decided to implement a framework for pluggable IM on Ecore, called Ecore_IM.

Ecore_IM is based on Gtk/Qt Input Method frameworks and works with pluggable so called immodules. So after writing the API for Ecore_IM I wrote a plugin hildon-input-method for accessing the maemo keyboard.

I already integrated it with Etk, so all Etk applications running on the device will automatically show the keyboard when requested. I intend to implement support for E widgets, so Mamona that is shipping with E can use the maemo keyboard.

If you are interested in using it or integrating it in your application you can grab it from here. The Etk support can be found here.

I hope this get integrated in Ecore really soon, so stay tuned.

N810 maemo submission accepted

N810 maemo submission accepted

Congratulations! You have been accepted to the N810 maemo device
program. We will send your discount and instructions as soon as the
device is available in your selected shop (soon).

Hooray! I can't wait to put my hands on my new toy!!!

GObject skeleton generator for Vim

So after reading this blog entry from Gustavo, I found it interesting and decided to do the same for Vim, as I would never use Emacs :D. So I found this script and did some small changes to make it fit better the GTK+ coding style.

To use the script first copy it to ~/.vim/plugin directory, then open a file with vim and run one of the commands:

• GOBGenerateH

To generate the class definition.

• GOBGenerateC

To generate the class implementation.

Both commands will use the filename as default for the class name. You can change it, by typing the class name manually. It will replace "-" with "_" and also try to apply Camel Case to the filename. For example a file named test-object.h will generate a class named TestObject.

If you are interested, you can download the updated version of the script from here