Some time I'm thinking about ways to get rid of the many string comparison when playing a SMIL file in KMPlayer. The flow of a movie is mainly written in tags and attribure values.
These documents have hardly any textnodes, so tags+attributes are about halve of the content, remaining is then the attribute values. So sharing these strings for tags/attributes would also be a great memory saving, making the DOM grow at 50% speed.

At Fosem when asked about motivation developing OSS, it's learning in my case.
I started the XML engine in KMPlayer when in my previous job, between projects,
I was reading some docu's about JavaEE, and getting bored reading I started

Mentioned in an older blog, I ported KMPlayer to the Nokia770.
Given that the GUI of a full KDE desktop and from this device are so different, I doesn't made sense to make fake QWidget classes for this port. However for utility classes like QString and KURL it did make sense. This weekend I ported the RealPix support to the N770 and benefiting greatly from these wrapper classes. The diff between these source files are no more than some include statements and lines where QString -> String.

What should one do if someone spreads FUD about a part of open source. Lets try the "why?" question.
So one bashes qt on #maemo, channel for this GTK based platform used by the N770. Names are mangled if not me.

Being in the N770 developments program and their great SDK/emulator, I really couldn't resist to try some programming for myself. Obvious choice is of course a port of kmplayer. The SDK is great and has both an i386 and arm target. The arm target uses qemu and is not capable of running GUI clients, but does run the console stuff, like configure scripts!!, this way.