Ian Monroe's Homepage

QtScript Bindings

If you've been following Peter Zhou's blogs, you know that he has been implementing QtScript support for Amarok. Probably the neatest thing we did is give access to almost the entire Qt API via the QtScript Binding Generator from Trolltech Labs. It uses technology from QtJambi; if you have Qt 4.4.1 and were wondering why Amarok gives a bunch of MetaJavaBuilder errors, this is why. (The bindings are disabled for Qt 4.4.0; we'll bump the Amarok dependency once 4.4.1 is more widespread).

I do think that the QtScript API is probably the most difficult Qt API to get the details right on. Your mind swirls with QScriptValue, QObjects and QVariants. But it is also quite powerful.

Since I had been sending the generators creator Kent Hanson emails regularly, I thought a mailing list would be a good idea to make it more public and useful. Join qtscript-bindings for discussion on the QtScript bindings in general. Kent also created a bug tracker and a Git repo. I created a mirror of it on repo.or.cz and posted the changes we've made to our SVN copy.

The beginnings of documentation for Amarok scripting are available and Richard Moore started a general Techbase article.

Console and Unnamed HTTP Server

The first script I created was an "irb" for Amarok's QtScript environment. This is available with Amarok SVN now, the "Amarok Script Console." It's quite handy to test out QtScript or to even test out the Qt API.

I've been working on a web control application for Amarok 2 using the new API. Using QTcpServer and QHttp, I have created a web server that should work well enough for what I'm doing. Now all that's left is the "little detail" of the HTML interface; I've been tinkering with qooxdoo, a very fancy JavaScript API.

One of my first sizable Amarok-related developments was to create the first kde-apps Amarok script in 2004 using Korundrum. So now its full circle.

Some Blog

The google news catcher sent me an indirect link to this Time-Warner blog: 3 Linux Apps That Make Me Hate Windows. He cites Synaptic, Compiz and Amarok. As much as you hear people gripe about package management on Linux, I really do think its one of its best features. Certainly from a security standpoint: going to a random web site and installing software just isn't something You Do on Linux, and I think thats for the best. And of course, it goes without saying that I agree Amarok is the best media player.

Everyone have fun at aKademy!

QtScript Bindings

If you've been following Peter Zhou's blogs, you know that he has been implementing QtScript support for Amarok. Probably the neatest thing we did is give access to almost the entire Qt API via the QtScript Binding Generator from Trolltech Labs. It uses technology from QtJambi; if you have Qt 4.4.1 and were wondering why Amarok gives a bunch of MetaJavaBuilder errors, this is why. (The bindings are disabled for Qt 4.4.0; we'll bump the Amarok dependency once 4.4.1 is more widespread).

I do think that the QtScript API is probably the most difficult Qt API to get the details right on. Your mind swirls with QScriptValue, QObjects and QVariants. But it is also quite powerful.

Since I had been sending the generators creator Kent Hanson emails regularly, I thought a mailing list would be a good idea to make it more public and useful. Join qtscript-bindings for discussion on the QtScript bindings in general. Kent also created a bug tracker and a Git repo. I created a mirror of it on repo.or.cz and posted the changes we've made to our SVN copy.

The beginnings of documentation for Amarok scripting are available and Richard Moore started a general Techbase article.

Console and Unnamed HTTP Server

The first script I created was an "irb" for Amarok's QtScript environment. This is available with Amarok SVN now, the "Amarok Script Console." It's quite handy to test out QtScript or to even test out the Qt API.

I've been working on a web control application for Amarok 2 using the new API. Using QTcpServer and QHttp, I have created a web server that should work well enough for what I'm doing. Now all that's left is the "little detail" of the HTML interface; I've been tinkering with qooxdoo, a very fancy JavaScript API.

One of my first sizable Amarok-related developments was to create the first kde-apps Amarok script in 2004 using Korundrum. So now its full circle.

Some Blog

The google news catcher sent me an indirect link to this Time-Warner blog: 3 Linux Apps That Make Me Hate Windows. He cites Synaptic, Compiz and Amarok. As much as you hear people gripe about package management on Linux, I really do think its one of its best features. Certainly from a security standpoint: going to a random web site and installing software just isn't something You Do on Linux, and I think thats for the best. And of course, it goes without saying that I agree Amarok is the best media player.

Everyone have fun at aKademy! I know I would be. :/

We're currently transitioning our blog from s9y to Drupal. For the time being people who blog on s9y itself are blogging there still, but the aggregation is already happening on Drupal so its a good time to change.

Add this feed if you want to follow the blogs of Amarok developers:
http://amarok.kde.org/planet.xml

As a Missourian and a person who thinks Belgium makes some of the best beer in the world, I've been following the story about the possible take over of Anheuser-Busch by Belgium beer-producer InBev with some interest. Personally I kind of want it to go through: it would hopefully mean the end of American beer being judged by its most tasteless examples. There is some good beer produced here. I think people would look at things differently if Bud Light becomes a Belgian beer.

It would also be very ironic and funny, which is mostly why I hope the deal will go through.

The article notes that "The takeover attempt has also run into a political backlash, as Anheuser-Busch, based in St. Louis, is an American icon. Senator Claire McCaskill, Democrat of Missouri, has vowed to stop the deal." Which got me thinking: I would personally find it hilarious if people in Belgium started rallying against this deal due to the damage to their national pride from having their corporations promote products like Bud Light. Any Belgian folks out there feel like writing their MPs?

Our biochemist-in-residence illogic-al just wrote a fun and interesting blog about Amarok on OS X. Interesting because it shows Amarok working on OS X, fun because it shows some of the progression of Amarok 2 in general.

Getting There
Yesterday I arrived in Taipei after about 22 hours of airplanes and airports. At least for a Missouri guy like me, it seems sparling and huge. Fellow Amarok dev and Sydney resident Seb Ruiz isn't so impressed. I didn't get lost on my way to the hostel until the very last block. I walked into a bakery probably looking quite lost (I had been walking around a single block for about 10 minutes) and one of the workers asked me "do you need help?" in English. I showed her the address and phone number of the hostel, she whipped out her mobile and called it, got directions and walked me to the entrance (about 20 meters away actually). So the Taiwanese are very friendly, Seb had a similar experience of someone actually taking him up the elevator directly to the hostel.

The hostel itself (the "Camel's Oasis"), is very homey. I found Seb chatting with a Québécoise about her 6-month world tour (you always find such lucky people at cheap hostels). I did follow Seb's advice and avoided sleeping much on the flight over here (only about 3 hours), but my biological clock still objected to the 11 hour timeshift; I had some pretty spotty sleep last night.

OpenTech Conference
Now we're at Asus for the OpenTech Summit. This morning is being devoted to Asus. Ellis, the product manager for the Asus EeePC (IIRC), presented on how Asus intends to work with the community. A Xandros developer, Brian, went over SDK for the Asus EeePC, which is basically Xandros distributed with Eclipse and Vmplayer. The main development environment they are supporting is Qt 4.2; he did a "Hello World" using Eclipse's Qt Designer integration. Both Ellis and Brian talked about the method for ISVs to release software for the Eee PC; this interests me since it would be really nice to have a way to release the newest Amarok's directly to the EeePC Add/Remove Programs system. The next version of the EeePC OS is apparently going to make it easy to install .deb's or an EeePC-specific tarball which contains a bunch of .deb files.

I know I promised on-going blogs on the Linux Collaboration Summit, but I failed. From previous experience I knew not to count on reliable Internet access at the conference site; I was planning to just post the blogs I had written during the day when I returned to the hotel. What I didn't count on was the conference rooms would have less electrical outlets then your average dorm room. We blamed the nearby super-computer for taking all our power. The important point is that the battery life on my laptop is about 15 minutes. So I was put in the ironic situation of going to a technology conference, but having access to very little technology. I did have a digital camera though.

From the whole conference there was a real sense of "hey stuff is actually coming together." Not that this will be the year of the Linux Desktop, but that Linux is positioning itself well as the solution for devices that go beyond the desktop. Like the lowcost Asus EeePC is a whole product category that Linux makes possible. The most interesting session on Tuesday was the Mobile roundtable, since there are several competing stacks: Intel has one based on GTK, LiMo has a variation of that, and then Google is building one from scratch (Qtopia was unrepresented). So in the same way you knew IBM was going to win-big with the now current generation of video games consoles (PS3, X-Box 360 and Wii), Linux is going to do well on the smartphone.

The Desktop Architects Meeting was informative, but I hope future meetings will feature more break-out sessions and actual action plans. Kevin mentioned that in DAM-3 they did something like this. The DAM has people from users to distros to upstream desktop developers. We all have a lot to learn from each other, but also different things that need to be worked out. For instance I had hoped for more work with Gnome developers.

An irony is that due to the LCS I'm probably going to give OpenSolaris a serious try. Brian Cameron from Gnome and Sun made a compelling case for their set of development tools when we were talking at the IBM reception. Basically it sounds like you can run a tool like Valgrind (dtrace?) that doesn't make the app your debugging run a magnitude slower.

The Firefox representative made a reference to this, he said that OS X is the best tool for Linux development. He was also concerned that Linux distros turn off their system for counting users, which is apparently part of their update system. Well obviously distros are going to want to turn off an update system, I wonder if Firefox even tried having a counting system separate from update? It would be in Linux's interest to have our Firefox's be counted so that Firefox knows how many Linux users there are. I asked him if they would join the growing ranks of Open Source projects with time-based releases, he more or less flatly said no. Of course that's what most of the crowd at aKademy said when Shuttleworth made the same suggestion, and look at us now.

The most useful parts of the Summit were making contacts with people from throughout the industry: some exciting stuff that's probably too early to talk about.

Tomorrow morning I'm headed to Kirksville Regional Airport and then eventually to Texas for the three-day Linux Foundation Collaboration Summit. I've never been to a non-KDE tech conference before; I'm really looking forward to it. There should be lot's of business types, I'm packing a lot of polo shirts instead of the usual Amarok t-shirts I'd wear at aKademy. Note to self: buy KDE-themed polo shirts.

Our hotel supposedly has Internet. So stay tuned, blogs are to follow.

Tomorrow is also the cut-off date for Google Summer of Code applications. For real this time. If you haven't sent in your Amarok application... realistically it's too late since we already have which ones we want in mind. Of course there's always a chance you're application could be better. I just realized the revised GSoC timeline worked out for me, since before I would've been in Texas during the last week of ranking.

Summer of Code is back, earlier then ever. Early is good as it allows some more flexibility in the schedule (students could start on their projects as soon as mid-April, in case they aren't available later), the disadvantage is that I'm probably not the only one somewhat surprised that its starting so soon.

So it's important to get the word out to prospective students. So if you're on any LUG mailing lists or any list with Computer Science students, send them a message about Summer of Code in general and about KDE in particular. Include a link to the SoC homepage, the Timeline and the list of KDE project suggestions*. Offer yourself as kind of the local contact to the open source "world".

I sent out such a email to my local LUG and found a few interested people. The common response was that they had wanted to get involved with open source but weren't sure how, the issue SoC is largely trying to solve. We had a meeting yesterday and it sounds like a couple of students will maybe even develop for Amarok. This is just at a small university... there's a lot of untapped potential out there.

*The suggestion list, at least for Amarok before I cleaned it up, had somewhat degenerated into people putting up feature suggestions (one not feasible, one that was more like a weekend project). Be sure to add project suggestions (for projects you actually know something about), but also double check the other suggestions. Always encourage the students to work with a particular mailing list or IRC channel to help refine the proposal.

Haven't blogged in a bit, so I have a couple unrelated blogs.

Dragon Player 2.0.1

Dragon Player 2.0.1 was released last week. 2.0.0 had a little but very visible bug (pressing the mute button would cause the mute button to disable), but luckly my sense of paranoia of such things kept me from advertising 2.0.0 outside of Dragon Player's website. Credit goes to a few years of Amarok releases going just a bit wrong at the last minute (though this year has been good to us).

Anyways I think Dragon Player 2.0.1 is a solid release. It'll probably be the last release of Dragon Player done independently, as now Dragon Player is a part of KDE Multimedia. We have a bunch of ideas for Dragon Player 2.1 (released with KDE 4.1). Mostly it all comes down to polishing the interface.

About the only difference between 2.0.1 and 2.0-rc1 is the new icon. Which looks utterly fantastic in my opinion. Credit goes to Eugene Trounev of the KDE games project. They have a great community spirit, it's no accident that KDE games was fully ready for KDE 4.

Quassel

While Europeans go to FOSDEM Brussels, drinking their great beer and partying with Mike, us Americanos are stuck looking at pictures and thinking how fun it could have been. Luckly this year something else came out of FOSDEM for us lonely folks: the public release of Quassel. My initial impressions wasn't good: it stalls when you join a channel or connect to a server. But it turns out that the way you use Quassel that doesn't really matter, since the "quasselcore" stays running and you basically never have to join a channel again. So for an alpha, it is very usable and I would recommend it, even if you're only interested in an IRC client and not something to test out. Yesterday morning I added mouse wheel support to Quassel's channel list; it was good to warm my Qt Model/View muscles some. I pretty much had to add it: I would try to use my mouse wheel every time I changed channels even though it never worked.

Some people (apparently everyone but me) experience crashing when they do the initial network setup for Quassel Alpha1. Alpha2 should be out shortly.