ShareThis

Here are some documentation pointers for Hildon desktop extenders:

• Writing Desktop Widgets in the draft Maemo 5 Developers Guide.
• API reference for libhildondesktop, a library for desktop extension developement.
• Python bindings for libhildondesktop.

In preparation for the event, I’d love to hear from people interested in the Hildon desktop, and specially from people developing home and status menu widgets.

Updated: The final Maemo 5 SDK has been released, I’ve changed the libhildondesktop link to the newest version.

ShareThis

ShareThis

ShareThis

ShareThis

This time it’s distributed version control systems, with discussions flaring up the Internet to decide which shall be The One DVCS to Rule Them All. And, once again, no surprises. The fast has won over the flexible, the cool has triumphed over the supportive, the macho has destroyed the elegant: Git’s won and Bazaar’s lost. Nothing new here, move along…

Wait a moment, though, as I’d like to make some suggestions to the major players in this epic battle that will not go into the programming annals, but only because we have none.

Git developers: Congratulations! You have created a good tool which, when you buy into its process, works superbly and –has anyone commented on this before?– it’s incredibly fast. Just be aware that not everyone works on the Linux kernel, and supporting different workflows is clearly an area of improvement.

Git supporters: You’ve won a battle, but not the war, and there’s much work to be done yet. Do not tolerate people using other tools, specially if they are constrained by their employers or customers. Keep proselytizing, in every venue, with your chants of “Faster, faster!”, because you know that’s the argument that always wins, that completely trumps any other. It’s also a good way of passing time until the next battle, because the world is imperfect and there will always be other people, other projects to ridicule.

Bazaar developers: You made something better, and you should have known that’s, unfortunately, worse. But your ideas can still be useful. That great plugin you wrote? Reimplement it for git, using a mix of bash scripts, Perl and C. It should take you three to ten times longer, but now you know your cycles are worth a lot less than your CPU’s.

Bazaar supporters: Yes, all three of you. Sorry, but there’s no prize for fair play, if that was what you were aiming for. Learn Git, it’s not as difficult as it’s said to be, and you’re intelligent people. Welcome to the Better is Worse corner of the world, there’s lots of interesting (but sometimes smug) people here and you get to say “That’s been done before, and better” a lot.

Other DVCS devs and supporters: Yes, I know you exist and are used in some project and each one of you is like a precious flower, unique with its pros and cons. But Git and Bazaar are the two extremes here, so apply one side or the other depending on whether you think your tool of choice has won or lost.

Everybody: Use a DVCS, it’s a clear improvement over previous tools. Also, read Worse is Better (extended version). And remember it next time around, please.

ShareThis

Please provide a small description of what the project does or at least a link to the main page. “Text Editor” is easy to understand, but many project names are not. What does PiTiVi do, and why is the Simple Timeline gone? What’s a gbrainy and why is it included in a CD? We really want to know!

Thanks and have a good day

ShareThis

I hope Adobe developers will repeat these tests, as they’ll have a lot more info than I do

ShareThis

The plugin work landed on r32766, while I was on vacation and away from the keyboard, so I just found out this morning reading Marco Barisione’s blog. So a lot of thanks to everyone who helped getting this working: My coworkers at Collabora, Alp Toker and Simon Haussman who reviewed the patch, Rodney Dawes who did the original code and everyone on bug #14750 for a lot of comments, help and support.

There’s still a lot of work to be done, though: Support for windowless plugins, Xt plugins on the Qt port, plugins that ask questions before having created a view like Acrobat Reader… But I think that now that we have the basic support in trunk, other projects will be able to test their NPAPI plugins on WebKit and catch those Mozilla-dependencies bugs.

ShareThis