AUG
1
2006

I hate telemarketers

I just got a spam call from some telemarketers called Eurointerview who are based in Germany. They seem to think that because they're not in the UK the telephone preference service doesn't apply to them, and presumably that because they're calling the UK the German laws don't apply either. If anyone has any spare junk mail they don't want they could give it to them at: EuroInterview GmbH, Hansestraße 69, 48165 Muenster, Germany. Phone: +49 (0) 2501-968-0, Fax: +49 (0) 2501-968-190,

MAY
21
2006

First steps towards Kasbar 4

Over the last few days I've started working a rewrite of Kasbar for Qt 4. This is a rewrite rather than a straight port because lots of the code in kasbar was there to work around limitations in X11 that will not apply once we have a composition manager. In addition, the old code was massively over complex because the features got added over time until the original design was swamped. I am however able to make use of some of the old code as basis for the new version, and many of the ideas will remain the same.

MAR
29
2006

KJSEmbed 4, small steps

I finally got some time to spend on KDE last weekend, so on Sunday I started working on a new binding generator for KJSEmbed on Qt 4. In the KDE 3 version I used Doxygen to generate XML output then processed that with XSLT (using xsltproc) to produce the C++ code for the bindings. Unfortunately this provded to be a bit too inflexible, and difficult for other developers (who weren't familiar with XSLT) to work on.

MAR
9
2006

KPassivePopup

Well, after a long break I've finally had a chance to work on KDE again. As a start, I've been trying to get KPassivePopup into a sane state in the KDE 4 libraries. The first step was moving all the internals of the class into the internal data class, which was a bit of a pain but pretty easy. To make things more interesting, it turns out that the API that worked fine on X11, is actually ambiguous on win32 and macos X due to different definitions of WId in Qt, the fix was to remove the ambiguous constructors (which I'd planned anyway as part of making a more Qt4-style API). The question moving forward is if this class needs to allow subclasses to define new visual representations (probably via a decorator of some kind), or if it's better to say there are the following presentation types and that's it. Does anyone who's using the class have any thoughts on this?

SEP
4
2005

Scripting, Malaga and KDE 4

I'm now back from Malaga and have just about recovered, so I thought I'd blog a little about the discussions etc. I've been involved in over there. For me, obviously, the big questions were about scripting. Until now, KDE has been weak in the area of scripting applications - this will not be true of KDE 4.

AUG
28
2005

Scripts with a KDE Feel

At the party last night I got asked to put my presentation from yesterday online. So, for now I've put it online on my website http://xmelegance.org/. Thanks to everyone who came, I hope you found it useful.

MAY
18
2005

Qt 4 Work

Some progress has been made on the Qt 4 front this week. I've implemented a simple QHttp based version of XMLHttpRequest that will ultimately be bound to KJSEmbed/Qt4. This will mean that the scripts will be able to access web based XML services such as news feeds, weather reports etc. I've now also got a working build environment to begin helping with the kdelibs porting effort.

MAY
11
2005

KJSEmbed 4

Well, I've just got back from London visiting my brother. A note for anyone who plans to visit the Turner Whistler Monet exhibition at Tate Britain - make sure you book. The queues are unbelievable, I've never seen anything like it at a gallery here.

APR
15
2005

Trinary operator in python

Here's an example of an easy and compact way to simuate the trinary operator in python. It is not short circuit like the one in C, but it is pretty simple:

  newowner    = [self.newowner, None][self.contactid == self.newowner]
APR
14
2005

The trouble with DConf

There's been lot of discussion on the XDG list about a proposal called 'DConf'. Unfortunately, it seems to me to have missed some rather important issues. The most obvious question in any sort of common configuration is system is 'What configuration can be shared?'.

Pages