First of all, this was the second time I attended to this hackfest (I “kind of” attended last year hackfest as well) but now things were pretty different for me, basically because one year ago I was not part of the Igalia WebKit team yet, hence my contributions in the hackfest were pretty small (see my post back then for more details). However, this time I attended full-time to the event and I must say I’m really proud of the work I’ve been doing right there, which I hope will eventually lead to the resolution of this WebKit metabug, which was about fixing bugs blocking ORCA support from WebKitGTK based applications.

But fortunately, the work I’ve been doing during the last week was just a pretty small and humble contribution compared to all the work that has been done by the rest of the people attending to the hackfest, like fixing GTK3 and GObject Introspection issues, fully integrating in libsoup all the new cache stuff written for WebKitGTK (which eventually lead to removing the equivalent code from WebKitGTK, as my mate Sergio told some weeks ago, as soon as some bots upgrade to the latest version of libsoup), adding support for profiling in JavascriptCore, implementing some missing and advanced features into the DumRenderTree (aka DRT, the so beloved tool for writing functional tests), fixing spell-checking support… and bugfixing in general (as well as, most likely, lots of other things I’m failing to recall right now). You can read Diego’s blog for more details on those.

Other than that, there was also time for working in Epiphany were some notorious fixes and improvements also happened. Those I can remember right now are the new error pages for epiphany, the implementation of a certificates viewer and new font preferences, getting rid of GConf in epiphany-extensions and general bugfixing tasks. As you can easily understand, as the devoted and committed Epiphany user that I am, I’m pretty excited with these improvements as well. Not needed to say anything about this patch committed at the beginning of the hackfest, I guess, in my opinion this is one of those cases where a picture is clearly worth a thousand words:-)

So, as you can see it was a quite productive week after all here in Coruña!

Last but not least, I’d like to specially thank The GNOME Foundation for sponsoring the event, as well as Igalia and Collabora for helping make this possible once again. Hope we can repeat it next year, and that more people will join the event to help making WebKitGTK an even better web engine for the GNOME platform.

See pictures of the hackfest here:

• My flickr photostream
• Joone’s flickr photostream
• Diego’s ‘webkitgtk’ tagged pictures

0 0

First of all, this was the second time I attended to this hackfest (I “kind of” attended last year hackfest as well) but now things were pretty different for me, basically because one year ago I was not part of the Igalia WebKit team yet, hence my contributions in the hackfest were pretty small (see my post back then for more details). However, this time I attended full-time to the event and I must say I’m really proud of the work I’ve been doing right there, which I hope will eventually lead to the resolution of this WebKit metabug, which was about fixing bugs blocking ORCA support from WebKitGTK based applications.

But fortunately, the work I’ve been doing during the last week was just a pretty small and humble contribution compared to all the work that has been done by the rest of the people attending to the hackfest, like fixing GTK3 and GObject Introspection issues, fully integrating in libsoup all the new cache stuff written for WebKitGTK (which eventually lead to removing the equivalent code from WebKitGTK, as my mate Sergio told some weeks ago, as soon as some bots upgrade to the latest version of libsoup), adding support for profiling in JavascriptCore, implementing some missing and advanced features into the DumRenderTree (aka DRT, the so beloved tool for writing functional tests), fixing spell-checking support… and bugfixing in general (as well as, most likely, lots of other things I’m failing to recall right now). You can read Diego’s blog for more details on those.

Other than that, there was also time for working in Epiphany were some notorious fixes and improvements also happened. Those I can remember right now are the new error pages for epiphany, the implementation of a certificates viewer and new font preferences, getting rid of GConf in epiphany-extensions and general bugfixing tasks. As you can easily understand, as the devoted and committed Epiphany user that I am, I’m pretty excited with these improvements as well. Not needed to say anything about this patch committed at the beginning of the hackfest, I guess, in my opinion this is one of those cases where a picture is clearly worth a thousand words:-)

So, as you can see it was a quite productive week after all here in Coruña!

Last but not least, I’d like to specially thank The GNOME Foundation for sponsoring the event, as well as Igalia and Collabora for helping make this possible once again. Hope we can repeat it next year, and that more people will join the event to help making WebKitGTK an even better web engine for the GNOME platform.

See pictures of the hackfest here:

• My flickr photostream
• Joone’s flickr photostream
• Diego’s ‘webkitgtk’ tagged pictures

5 0

I’ve arrived yesterday to Den Haag, along with most of the Igalia gang (still some of us coming tomorrow), and will be here just until Friday  morning, since I’ll need to miss the last day of GUADEC to attend my brother’s wedding. So, don’t hesitate to talk to me if you see me hanging around and want to share something, chat, or just to get a nice Igalia shirt… or even something different, who knows…

For more information, I’ll basically be in the Haagse Hogeschool most of the time during the day, and maybe in the hall of the hotel at night, although I can’t promise much about that because the time slot after dinner will be the only moment I’ll have to walk around the city in this my first visit to the Netherlands.

And by the way… if you’re expecting to see a long hair guy I must warn you that won’t be possible, at least for the moment.

And that’s all, I guess… see you in GUADEC!

PS: Did I say we have a new website? Check it out here.

0 0

I’ve arrived yesterday to Den Haag, along with most of the Igalia gang (still some of us coming tomorrow), and will be here just until Friday  morning, since I’ll need to miss the last day of GUADEC to attend my brother’s wedding. So, don’t hesitate to talk to me if you see me hanging around and want to share something, chat, or just to get a nice Igalia shirt… or even something different, who knows…

For more information, I’ll basically be in the Haagse Hogeschool most of the time during the day, and maybe in the hall of the hotel at night, although I can’t promise much about that because the time slot after dinner will be the only moment I’ll have to walk around the city in this my first visit to the Netherlands.

And by the way… if you’re expecting to see a long hair guy I must warn you that won’t be possible, at least for the moment.

And that’s all, I guess… see you in GUADEC!

PS: Did I say we have a new website? Check it out here.

4 0

Perhaps you’re thinking why the hell I needed frogr to upload pictures when the N900 already comes with a nice and handy sharing application to upload pictures directly from the camera app or the image viewer, so here you have some use cases where I found the  sharing app not enough for my needs:

• To upload several pictures in a row to flickr, instead of having to do it one by one (tipical use case after taking several pictures that I’d like to share/backup in flickr).
• To set same name, description and/or tags to a bunch of pictures instead of doing it one by one (related to previous use case).
• To be able to upload pictures as “private” instead of “public”.

Update: I’m correcting this post here since it seems the sharing application already was capable of doing some of those things I mentioned above (ups!). Anyway, as I commented there, this does not discourage me even a little bit of keeping porting my little frogr to Fremantle, but just encourage me to try to make a difference and because… why not to tell it? I’d just love to bring frogr with me wherever I go :-). Thanks Daniel for your comment!

Current status of this port to Fremantle is still work in progress so don’t expect to find anything working out-of-the-box if you download the source code at this moment, but the idea is to get it into a stable state soon to upload it to maemo-extras, along with a packaged version for Fremantle of the great flickcurl library, which is a requirement for frogr to work (and at this moment I’m jsut packaging and using it on my own for development purposes).

[*] I think the screenshot explains pretty well the main reason why I work so slowly and at late hours in frogr :-)

0 0

Perhaps you’re thinking why the hell I needed frogr to upload pictures when the N900 already comes with a nice and handy sharing application to upload pictures directly from the camera app or the image viewer, so here you have some use cases where I found the  sharing app not enough for my needs:

• To upload several pictures in a row to flickr, instead of having to do it one by one (tipical use case after taking several pictures that I’d like to share/backup in flickr).
• To set same name, description and/or tags to a bunch of pictures instead of doing it one by one (related to previous use case).
• To be able to upload pictures as “private” instead of “public”.

Update: I’m correcting this post here since it seems the sharing application already was capable of doing some of those things I mentioned above (ups!). Anyway, as I commented there, this does not discourage me even a little bit of keeping porting my little frogr to Fremantle, but just encourage me to try to make a difference and because… why not to tell it? I’d just love to bring frogr with me wherever I go . Thanks Daniel for your comment!

Current status of this port to Fremantle is still work in progress so don’t expect to find anything working out-of-the-box if you download the source code at this moment, but the idea is to get it into a stable state soon to upload it to maemo-extras, along with a packaged version for Fremantle of the great flickcurl library, which is a requirement for frogr to work (and at this moment I’m jsut packaging and using it on my own for development purposes).

[*] I think the screenshot explains pretty well the main reason why I work so slowly and at late hours in frogr

11 1

By the way, and talking about the Ice Cream Deathmatch, I have to say this was my first time taking part of such a contest and now I understand why it is a DEATH-match… as today I woke up with a “sugar-overflow failure” which will probably keep me away from more ice creams for some days :-)… you know, I need to survive yet another year to take part in the next edition of the contest :-)

At last I’d like to share with you a nice picture of the Jam session performed by some GNOME musicians:

Jam session at the Igalia Party

Keep on rockin’ me baby…

0 0

Thus, even though I had a great time last year in Madrid and Istanbul, I’m sure this time we’re going to have fun as never before and that it will be a perfect environment for sharing ideas, thoughts, knowledge… and perhaps even some beer at the wild parties social events both with the GNOME and KDE guys ;-).

I’m really really looking forward to being there with the rest of Igalia gang to start enjoying “the Guadec experience“… can’t actually believe I’ll be there just in three days! :-)

See you there guys!

0 0

It looks like a original and very visual idea to put many ideas and visions all together, doesn’t it? Pointless to say I agree more with the “love” side, of course :-)

By the way, I took this picture today, the second and last day of the conference… so now I’m ready to give a full and complete opinion about it, which is that it just was great: I had a very  good time and a lot of fun being there, and not only because of the talks, which were amazing in most of the cases, but also because of meeting people and sharing visions and comments with all of them.

So, it seems now it’s time to get back home, so now I’m going to bed, since I’m very tired and tomorrow I’ll have to wake up early to take the plane.

0 0

But… what the hell? That insane amount of talks and hackers hanging around is exactly which makes FOSDEM great, isn’t it? So, no complaints, only good words for FOSDEM! :-)

As I side note about conferences, I’d like to state I liked a lot the talks I attended, specially those ones in the “GNOME developers room”, which were all great. In a more specific way, I specially liked the talk about the People Framework, which is IMO such an interesting project, which could become a very helpful tool for those kind of people that, like me, suffer the typical problems of having several devices or applications with independent (but related) contact list. Keep going on with that awesome work, guys!

Regarding to the Fosdem Beer Event, needed to say it was just great to be there, talking to so many people (some new people to me, and some already “old friends”) and trying so many different beers, which were very tasty indeed, like the “Delirium Tremens” and “Kasteel”, for instance, which I just loved. The only slightly negative point on this was that trying so many beers didn’t help me to wake up in my best shape precisely, but nothing that a good breakfast and some hours of good talks could not fix :-).

At last, as a picture is usually better than too much text, here you are one: me in the main entrance.

Can’t wait for tomorrow!

0 0

https://garage.maemo.org/pipermail/vagalume-devel/2008-June/000151.html

…today I’ve finished the implementation of a new patch for Vagalume which will enable D-Bus support in the desktop version of this nice player, since so far D-Bus interaction was only allowed in the maemo platform (due to using functions from libosso for RPC methods, instead of dbus-glib).

So, this is how the vagalumectl script (formerly known as vagalume-dbus) would work from now on in a “regular” GNU/Linux machine:

mario@bender:~$ vagalumectl
Usage:
vagalumectl
(Vagalume will be automatically started if not already running)

COMMAND:
play:              start playing the current radio
skip:              skip to the nex song in the current radio
stop:              stop playing the current radio
love:              mark the current song as ‘loved’
ban:               mark the current song as ‘banned’
tag :         change to a ‘global tag’ radio.
artist :   change to a ‘similar artists’ radio
group :     change to a ‘last.fm group’ radio
loved :      change to a ‘loved’ radio for a specific user
neighbours : change to a ‘neighbours’ radio for a specific user
personal :   change to a ‘personal’ radio for a specific user
playlist :   change to a ‘playlist’ radio for a specific user
playurl :     just play the specified URL on Vagalume
volumeup [INC]:    increase playback volume
volumedown [INC]:  decrease playback volume
volume :    set the playback volume to a specific value
start:             start Vagalume (if not already running)
close:             close Vagalume (if not already closed)
help:              print this information

Double quotes are REQUIRED when specifying parameters to some commands,
such as TAG or ARTIST, because of the white spaces they might contain, e.g:

$ vagalumectl tag “hard rock”
$ vagalumectl artist “Led Zeppelin”

mario@bender:~$ vagalumectl loved homemaxico
Command ‘loved’ successfully executed
mario@bender:~$

Well… perhaps not a too much useful ‘screenshot’ after all… but believe me, that’s the proof that D-Bus is working fine on my GNOME desktop from now on.

I hope you can enjoy the patch soon (as soon as Berto applies it to the SVN trunk)… perhaps in Vagalume 0.7 ;-), who knows…

0 0

After that, I thought it could be a good idea to implement a freedesktop tray icon as well, so you would be able to hide/show Vagalume with a tray icon in the notification area, in the same way you could do it with some other programs such as pidgin, xchat or rhythmbox, for instance. Moreover, some people told me that it would be very nice to have a tray icon in the desktop version of vagalume, so everything seemed to say that I was not mad after all and that it could be a good idea…

So, I’ve started working on its implementation (using a GtkStatusIcon) some weeks ago and now I finally managed to get the enough ‘spare time’ to plug everything together and to finally finish the patch for being applied to one of the latest revisions of the SVN trunk (158). In fact, at this moment I’ve already sent it to vagalume-devel@maemo.org mailing list and I’m waiting for Berto to take a look into it to finally integrate it for (hopefully) the next release :-)

Update [2008/04/29]: After working a bit more on this new tray icon during the past weekend I’ve added libnotify support to allow the tray icon to show a notification each time Vagalume starts playing a new song. Of course, as I know there’re people who might dislike this feature, I’ve also added the possibility of disabling these notifications from the ‘Settings’ dialog in the GNOME version of the application. I’ve also added an screenshot of the notifications working at the end of this post.

To finish with this post, and knowing that sometimes an image is better than just a description, here you are a couple of screenshots of the new tray icon working in my GNOME environment:

Vagalume’s tray icon: showing the menu

Vagalume’s tray icon: showing the tooltip

Update [2008/04/29]: Vagalume’s tray icon: showing playback notifications

And that’s all. I hope the patch is good enough to integrate it with the next release of Vagalume. Of course, suggestions and criticisms are always welcome, so don’t hesitate to leave your comments here.

I hope you like it ;-)

0 0

So, yesterday I spent some time looking for an easy and effective way for showing people attending to the talk how cool this cute device (my N810) is… and thinking about the past I remembered when Andres gave a talk/workshop about the Maemo development platform, where he used an VNC server installed in the device to show the N810 “screen” to everyone in the room, just using an VNC client in the laptop connected to the proyector.

IIRC, Andrés compiled the VNC server for the device to get it working, but yesterday I found a much easier way to get it working, so here you are the receipt (I use too much this word in my blog, perhaps I should consider to become a cook… ):

• Download the pre-compiled .deb package for your device from this web.
• Copy the .deb file to your device and install it following one of the following methods:
• Install it with the Application installer from the Control Panel (N770).
• Install it with the Application Manager from the ‘Settings’ Menu (N800 / N810). It’s required to have the red-pill mode enabled. To know how to enable this “peculiar” mode, check this out.
• Open a root terminal in the device with a remote ssh connection and install it this way:

dpkg -i x11vnc_0.9.3-1_armel.deb

• Configure it to use a password with the default username available in the device (‘user‘):
• Make sure you are running the terminal as ‘user’, by executing the command:

su user

• Create a VNC password (recommended):

x11vnc -storepasswd

• This will store your password (encrypted) under /home/user/.vnc/passwd
• Start the server:
• Not using the password: from Menu -> Extras, click on x11vnc.
• Using the password (recommended):
• Open a terminal for ‘user’
• Execute the command:

x11vnc –usepw

• Connect to server (already running on the device, at port 5900):
• Using any VNC client connect to your device’s IP, using the following credentials if you started the server with –usepw:
• Username: user
• Password: (whatever you’ve set with –storepasswd)

Of course, there are lots of options you can pass to x11vnc (see x11vnc –help) but these ones worked fine for me: I have an easy VNC server working with password authentication :-)

And to finish this post, just a last advice: If you think you’re going to use always (like me) the VNC server with password authentication, it could be more nice for you to edit the /usr/bin/x11vnc.sh script so it also includes the –usepw. This way, you can always start the VNC server from Menu -> Extras, withouth having to open a terminal for it… although, to be honest, I still prefer a remote terminal for most of the times, because of the output I continously get through it… but hey! that’s just a very personal opinion! :-)

0 0