So the BBC is making a new drama series about the battle between the ZX spectrum and the BBC Micro. Currently codenamed ‘Syntax Era’. As it turns out Clive Sinclair, the creator of the ZX Spectrum, had his offices very close to the current Collabora office here in Cambridge. And due to our own Edward Hervey knowing some of the people involved, the production team behind this new series came by our offices to do some location scouting some weeks ago. It is a little bit up in the air if they are going to use our offices or not in the end, but there is a chance they will, and if that happens there is also chance you might catch some familiar faces as extras in this new series 
O Firefox 3.5 foi lançado, e essa é uma boa notícia. Significa que os navegadores livres e/ou que respeitam padrões abertos continuam deixando comendo poeira os navegadores legados com o Internet Explorer (especialmente o 6, que ninguém merece, né?).
Entre outras coisas, o Firefox 3.5 tem performance de javascript muito melhor, parecida com a do Epiphany 2.27.3, e suporta bastante coisa de HTML5, incluindo as tags de audio e vídeo. Muito importante com relação a isso, é que ele suporta por padrão os formatos abertos (assim como a WebKitGTK+, que usa GStreamer, mas o suporte às tags ainda não funciona 100%). Tem algumas páginas muito interessantes para acompanhar a ‘adoção’ da nova release: http://downloadstats.mozilla.com/.
As pessoas devem saber da minha relação de amor é ódio com a Mozilla - mesmo hoje o navegador não se integra bem com meu GNOME, a API de embedding deixa muito a desejar, mas ninguém pode negar que o Firefox foi o que trouxe um clima de abertura para a Web, e exigiu que todos começassem a se preocupar com padrões, desempenho e qualidade. Se você usa um sistema operacional proprietário, largue logo os navegadores proprietários e use uma coisa que presta! =)
Sat. 4 July
"QtScript bindings for Telepathy" - lightning talk by Ian Monroe, 15:30-16:30
Sun. 5 July
"The location-aware desktop" by Beaudoin, Pierre-Luc with Henri Bergius: 11:30, Room 2
"Profiling and Optimizing D-Bus APIs" by William Thompson: 12:30pm, Room 1
"Integrating VideoConferencing into Everyday Applications" by Olivier Crete: 12:30, Room 4
Tues. 7 July 2009
"Let's make GNOME a collaborative desktop" by Guillaume Desmottes: 11:00 - 11:45
"How to play libnice-ly with your NAT" by Youness El Alaoui: 15:00
"Pitivi Video Editor" by Edward Hervey: 15:45
Thurs. 9 July 2009
"Introduction to GStreamer development Tutorial" by Wim Taymans: 15:00
Fri. 10th July
"Tools for Authoring Awesome Docs" by Davyd Madeley: 11:00
Be aware that harddisks are quite intelligent beasts those [sic] days.
...
I hereby speculate that harddisks can use the spare remapping area to secretly make copies of your data. Rising totalitarianism makes this almost a certitude. It is quite straightforward to implement some simple filtering schemes that would copy potentially interesting data. Better, a harddisk can probably detect that a given file is being wiped, and silently make a copy of it, while wiping the original as instructed.
So in preparation for heading of to Gran Canaria and GUADEC on Thursday I pushed a new Transmageddon release today. 0.11 is actually the first release I posted to sites such as Gnomefiles and Freshmeat so in some sense I guess I feel more confident about this version that earlier ones. A lot of new features included, like multipass encoding, videoflipping (so if your video is 90 degrees tilted you can correct that during transcoding) and better profiles. Still kinda rough at the edges though, and the very latest GStreamer releases are needed for everything to work. Still expecting quite a few bugs to be reported still.
In some sense development have stood still for a while as I have focused on testing various devices and GStreamer features. Remuxing is still on my todo list, but discovered that for instance an ac3parser is still needed in GStreamer to
do nice DVD conversions.
Was kinda nice to successfully use Transmageddon for a business related need at work, we had gotten a request at Collabora Multimedia which meant I needed to transcode a video into quicktime+h264+aac from a .vob file. Worked like a charm I mean while I have of course done hundred of transcodes as part of development, it was nice to do one for something ‘real’
I’m writing this on the plane back from Freiburg, and the Nepomuk Coding sprint. It’s a beautiful town (except late at night during the weekend, but anyway…) and well worth visiting again (hopefully there’ll be a Nepomuk Sprint 2010).
Now to the important details. As I often seem to at these kind of events, I find myself leaving with less code written than I arrived with. However, when put in context, this is no bad thing. Nepomuk is a new technology, and is not entirely straight forward for a newcomer to understand. I arrived with intentions of integrating Telepathy with Nepomuk, but with little clue how to actually do this. And the results: I know understand enough about how Nepomuk works to make a plan, and start coding on integrating with Telepathy (unfortunately most of the code I wrote in the few days beforehand with this aim turns out to be so wrong it’s best just to throw it away and start again).
There are two ways in which Telepathy will be integrated with Nepomuk. One is the fairly obvious case of storing metadata about your IM buddies. Some examples of this might be: the last time they were seen online or the geolocation at which they were last online using the Location interface of Telepathy). I’d love to hear any more suggestions of metadata that it might be good to store on your instant messaging and VoIP contacts (please use the comments section at the end).
The second integration point is a little different. It concerns the idea of metacontacts. Users of IM clients such as Kopete are probably familiar with the idea that you can group two buddies on different protocols, who are the same person in real-life, together as one metacontact. I intend to implement this for Telepathy applications’ contact lists using Nepomuk to store the relation between the different buddies. The advantage of doing this is that not just your IM client, but any Nepomuk enabled application can see this relationship.
So, that’s my rather superficial hand-wavy summary of the plans that came out of the Nepomuk sprint for Telepathy. I hope to write again soon to provide a mercilessly technical explanation of how all this will/is being implemented.
Finally, I’d just like to say thank you very much to Sebastian Trueg who did such a great job of organising this sprint.
Friendly reminder: the days left to vote to select foundation board members are running down!
Make it happen here: http://foundation.gnome.org/vote/vote.php?id=13
Photo (cc) by caribb: a typical sight during elections in Montréal, Québec.
It is my first participation in a such an online election, non national election. Of course I am exited to be part of it. Unfortunately, electronic voting makes a quite boring “Election’s night”. I am used to the 3 or 4 hours of febrile waiting before the people’s choices are announced. Where are the exit polls? 
Really. I mean, really indeed.
After updating to Fedora Core 11 I noticed a new feature, the automatic font download system. Essentially it works like the automatic codec download system we have in GStreamer, but for fonts.
So judging by how often the font download box pops up the spam I am getting these days seems to be mostly in 3 languages Coptic, Syriac and N’Go I have to assume the spams are using random character sets to confuse spam filters, as I doubt that for instance either the ancient egyptians or their Coptic descendants of today are a big enough demographic for the spammers of the world
I haven’t written anything for a couple of months now for the same reason that I haven’t committed any code. Exams. Now they’re over it’s back to hacking. But just because I haven’t been working on Telepathy/KDE for a while doesn’t mean that nothing has been done (obviously).
The underlying TelepathyQt4 library on which all our work is based has progressed a lot, gaining support for requesting channels from the Channel Dispatcher, gaining the Client interfaces and going through what will almost certainly be the last major API redesign before it goes stable. These two advances mean that it is now possible to work on Telepathy client applications in Qt/KDE without having to play an endless game of API catch-up.
There are also two summer of code projects progressing nicely:
- George Kiagiadakis (gkiagia)’s work on KCall is really exciting… I can’t wait to take part in my first video conference using KDE software!
- Kaushik Saurabh (roide) is also making great progress on his Conversation Logging Framework for KDE (while not entirely a Telepathy project, it goes without saying that the two will be integrated).
And now to the future… to Friday. I’ll be at the Nepomuk Sprint in Freiburg working on integrating instant messaging buddies with the address book and the semantic desktop. I’m not yet exactly sure how this will be done, but I’ll be spending the next 2 days up until the sprint getting that nailed down, and then coding madly once I get there. I really hope there can be something photogenic as a result, since libraries provide very limited picture-potential for this blog.
In the last weeks I have been asked several times to modify some components I’m working on to add the ability to split a full name in its components (first name, family name, etc.).
It looks like most people have great expectations about this working correctly but they get annoyed when it fails, and you can be sure it will fail. It will fail because it’s impossible to parse a name correctly, for instance:
| Full name | First | Middle | Last |
|---|---|---|---|
| Barack Hussein Obama | Barack | Hussein | Obama |
| Pier Silvio Berlusconi | Pier Silvio | Berlusconi | |
| José Rodríguez Zapatero | José | Rodríguez Zapatero |
How can you do this automatically?
This becomes particularly silly if you cannot be sure that the string you are going to parse is actually a full name, for instance don’t try to parse a chat nickname. It’s true that gmail/gtalk uses your full name by default, but this is only a default and it’s true only for gmail.
To cut a long story short, please please please don’t try to parse names. You can see by yourself how hard it is, even if I’m just considering western-style names.
If you still don’t trust me here’s a quote from e-name-western.c, i.e. the file that does name parsing in libebook 
:
* <Nat> Jamie, do you know anything about name parsing? * <jwz> Are you going down that rat hole? Bring a flashlight.
On a side note when you are trying to understand why some code is broken you can find some funny commits, like the great EDS purge
Update: I found this “serious” bug in e_name_western_parse 
.
Young student dentist Stringer was the one to phone me up to set up an appointment. He was more deft, gentle, and patient than several DDSes I've patronized. "Oh, you build up a lot of calculus here, because of your salivary gland. I have that too," he confided. He checked in with me about whether the ultrasonic cleaning dealie was running too hot and hurting me. "I don't like to use it, I don't think it's gentle enough," he said. He handed me the suction wand: "Raise your hand if you need me to stop so you can suction."
In further stereotype-demolishing, Stringer does not play World of Warcraft (nor does he wear Ira Glass glasses). My cousin-in-law-in-law Aaron, husband of Kristen, is on the road to full Dentistdom and enjoys WoW-style games. [pun about grinding omitted]
I told Stringer what his last name means in journalism; in retrospect, he has a new occupational surname, like Smith or Cooper.
I get curious about others' occupations. Firefighters, CAD designers, directors, transcriptionists, silversmiths, pastors, teachers, full-time caretakers, taxi drivers, deli owners, X-ray technicians, soldiers, construction workers, dentists. How does doing your job change the way you interact with others?
Last January, I announced Geolocation in Empathy. All pending branches have now been merged and released in Empathy 2.27.3.
It took quite a lot of time to finalize it because we were quite busy and quite frankly while this is sexy, it isn’t a very important feature in Empathy :-). In the following screenshots, you’ll discover that things have changed a lot since the original announcement.
First of all, the markers now include more information about the contact. This uses the new markers in libchamplain. It works nice for now (as I only have 3 or 4 contacts publishing their location), we’ll see with usage if the markers are just too big.
The map is now interactive: right clicking on a contact will bring up the same context menu you get on the contact list.
The Preferences UI was reworked to be simpler. The previous UI left space for an hypothetical Manual address mode which was dropped. The rationale is that Empathy shouldn’t have to care about addresses. If you want to change the address, change it in Geoclue.
This is new since January: the tool tip now include your contact’s geolocation information. This is the only part of all the geolocation changes that are present even if you don’t build with Geoclue or libchamplain. It was impossible to display a map there as ClutterGtk doesn’t seem to like such windows hehe. We already know it is partly ugly and contains duplicate information It will be improved before final release.
Finally, the contact information dialog now displays a map and the detailed information about the contact’s location.
Don’t miss the FAQ that I populated with questions I was often asked during development. Report bugs on the Geolocation component of Empathy (you can also see that we have work left to do).
I am not the only one who worked on this exiting feature, here are the details:
I can’t wait to see more people using this and show up on my map!
Long time without empathy blogpost. Lots of things happened in the Empathy/Telepathy world recently. Here I’ll present 4 new exciting feature of the upcoming Empathy 2.27.3. It will be an impressive release with not less than 49 bugs fixed!
Adium
The one year old adium branch got finally merged. This adds support for Adium Message Style themes in empathy. Themes are made of html and javascript, rendered using WebkitGtk. Of course webkit is optional dependency and old style themes can still be used.
Unfortunately all themes are not totally supported yet. Please check our wiki page for more information.
Geolocalisation
Another long standing branch got merged into Empathy master to add geoclue and libchamplain support. That means that you can now publish your position to your contacts. Your position can be calculater based on a connected GPS, based on your IP, or set manually to a postal address. You can of course tweak Empathy preferences to not publish the exact position for privacy.
If you have contacts publishing their position in your contact list, you’ll be able to see a world map with a marker at his position. The map is rendered thanks to libchamplain and animated using Clutter. Of course the map data is provided by OpenStreeMap.
This was done by Pierre-Luc Beaudoin and he will blog soon with more details and mandatory screenshots.
Desktop sharing
Work has been done to share your desktop with your contacts. This is done by creating a Telepathy StreamTube with your contact and passing the VNC protocol through it. Telepathy StreamTube spec is now undrafted and considered stable.
Guillaume will soon blog with more details about this.
File transfer
And last feature: The file transfer support in Empathy got large improvements. It now support checksum to make sure the transfer succeeded, and soon will support resume.
Some time ago I put out a request for someone to pull the AMR code in Android out and turn it into GStreamer plugins. Well Iago Toral Quiroga did exactly that and thus we now got support for encoding and decoding AMR-NB in GStreamer, combined with support for decoding AMR-WB. This turned out to be an indirect team effort as the current code is a combination of the original Android code, combined with some API glue code developed by Andres Mejia and Martin Storsjö, combined with the old AMR plugins in GStreamer which was meant to be used with some non-distributable reference code. These 3 code bases Iago massaged together into something pliable. The current plan is to merge the patch once bad and ugly unfreeze and we finally got some decent AMR plugins for GStreamer. A big thanks to Iago and everyone else involved.
This effort also fit in well with a bug hunt I have been on for a while to figure out why Transmageddon was not able to create files my phone could play back. After having spent a lot of time expanding on the transcoding engine in transmageddon and testing every possible variation I could come up with, it was finally Mark Nauwelaerts here at Collabora Multimedia who came to my rescue with this patch. Also that getting merged after the freeze.
Also been testing the ASF muxer that Thiago Sousa Santos is working on as part of this years Summer of Code. It is coming along very nicely, with WMA2 and WMV2 muxing working. Hopefully when I do my new Transmageddon release before heading down to Gran Canaria I can include ASF support too. Already got a nice batch of features in git master with multipass encoding, a lot of bugfixing to the profile support, h263 and video flipping. So with the efforts mentioned above I should also be able to add AMR-NB and ASF/Windows Media support to the mix too. I also hope it is a long time until the next time I need to think about stuff like pixel aspect ratio versus display aspect ratio
I still need an icon for Transmageddon if someone is up for the task.
LWN got a really interesting article discussing how Google have included H264 and AAC support in their Chrome browser using ffmpeg and the legal discussion that has come from that. It seems Chris DiBona and the Google lawyers have decided they can work around the LGPL by licensing patents for the ‘application’ instead of for the library implementing the functionality in question. Of course most of us would think that if you ship a library as part of your application, it is a part of your application, but Chris DiBona seems to feel that he licensed the H264 codec for use with the bookmarks list of Chrome and not the media engine
More seriously though DiBona tries to weasel out of the situation by claiming that the language of the LGPL saying ‘For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. ‘ only applies if there is a specific language in the patent license hindering re-distribution of the code. He even manages to refer to the fact that the FSF made the language on this subject even clearer in the LGPLv3 as proof that his reading is correct. While at the same time claiming that what the FSF thinks about these issues is irrelevant.
Well I guess Chris is right about Google taking their responsibilities very seriously, at least as long as they say what he wants them to say Can’t help but feel that Google somewhere along the line went from ‘do no evil’ to ‘we are google, hence no evil can have been done’ which while sounding similar actually are very different.
Funniest part though is that another part of Google, Android, seems to think its not even legally fine to ship a LGPL media framework combined with Apache licensed codecs with their stack. But I guess the Android and Chrome departments have different lawyers, so if we are lucky maybe the Android department ends up suing the Chrome department 
Or maybe Chris DiBona wakes up and realize he could resolve this issue quickly by combining the Apache licensed H264 implementation in Android with his ffmpeg stack and thus resolve this issue.
While deploying Geoclue with friends, I came to the conclusion that we need a GUI tool for end users to setup Geoclue. Geoclue-properties was born. gstreamer-properties was an inspiration (for the name, and part of the visual aspect).
I started the project only last Monday night, but you can already do this with it:
Just the last items save the user of having to use dbus-send incantations. For the screenshot lovers, here’s your dose.
The project is still quite embryonic. It is my first attempt at using Python for such a task and I lack knowledge (and quite frankly time) on how to create the project’s infrastructure (almost as if I am missing autotools — scary!). If someone is willing to contribute that or point me the doc I’d appreciate!
I just released the 0.6 version of my Elisa/Moovida RTBF plugin. The goal of this release is to integrate better with Moovida's user interface.
- Fix "Use this plugin" hook with Moovida. - Use new, Moovida style, square icon. - Move radios menu to "Internet -> Radio"
It should hopefully be available through Moovida's plugin section next week.
Well, not really my first patch. But the first thing I tried to mess with when I first started looking at WebKitGTK+ was the WebKitNetworkRequest object, because I was fancing the idea of writing stuff such as HTTP transactions monitoring, and things like that. So I wrote a big patch which exposed the internal WebCore object (ResourceRequest) fully through our own object. That was back in early 2008. We have come a long way since, and through all these months I got a broader perception of what kind of APIs we need, and how WebCore works. We also decided on going soup-only, which had a huge impact on what the final patch actually looks like.
The patch which finally got committed this week is, how can I put it, VERY different from what I had originally written. You can take a look at the long discussions about it in the bug report I used to track progress. I think I should point out that Marco Barisione and Christian Dywan were crucial in helping me get going with my contribution to WebKit at that time.
What this change gives us is basically the fact that a WebKitNetworkRequest now carries more than just the URI for the request (it actually carries with it a reference to the SoupMessage that will be used later in the request processing, which we are planning to expose in the near future), meaning that when WebKit API gives you a request, and you use it to cause a new load (for, say, opening in a new tab), you still get all the headers that were supposed to go with the request, so you don’t lose things such as, for instance, Referer. So, now, after more than 5 years, the bug that complained that Epiphany did not set Referer (and Galeon before that) for new tabs is finally closed.
By the way, this problem has been fixed for Mozilla’s browser back in 2002, but the embedding API is still buggy up to now. There is still hope, since there’s an attached patch that fixes the issue to be reviewed, and landed. If anyone is reading, it might be a good oportunity to get this fixed in there as well, so that users of applications that use Gecko’s embedding API can also benefit!
The PiTiVi team is very proud to announce the first release in the unstable 0.13 PiTiVi series.
This release is in memory of those who have lost their lives, friends, houses in the April 6th 2009 earthquake in l’Aquila, Italy.
You will find more info of the changes, bugfixes and so forth in the online release notes here .
To sum up this release :
This is not the end, far from it. We’re already working on the next 0.13.2 release which should be available just before the Gran Canaria Desktop Summit in July with exciting improvements like : transitions, mixing, effects, more speed/memory improvements…
People say an image is worth a thousand words… then I guess a video is worth a million words. Jean-Francois did a screencast showing off the latest features of PiTiVi… and of course edited it with PiTiVi. You can find it in ogg or on youtube. Thanks Jean-Francois !
Enjoy the Show !
Just got back from Cambridge, where I spent an all too brief time with many wonderful people, such as the Collaborans, and Katie, and ghoti and family. I'm very glad of all of you.
I found Fin's twenty-four hour comic from 2006 again today. Worth re-reading.
Also, what Maemo 5 needs is robotfindskitten. Definitely.
Seen quite a few very positive twitter feeds since Edward Hervey announced the 0.13.0.2 pre-release of the PiTiVi video editor. Also saw this blog entry by Bryan Lunduke praising our latest efforts around PiTiVi. So all Pitivi sceptics out there, this is the time to give PiTiVi another look!
Transmageddon
Nathan Willis wrote a nice article on lwn.net covering Transmageddon and Arista. If you are not a lwn.net subscriber you should seriously considering becoming so, or you just have to wait until the article becomes generally available next week.
To avoid scaring to many people away I also I finally updated the Transmageddon website today, so instead of looking like a 5 minute website it now looks like I at least gave it about an hour