Oh, also, qtHaskell. :yaay: I’ve wanted this for so long (well, since I knew about Qt and Haskell, which I suppose isn’t that long), and, and, it’s exactly what I wanted!

Except for the inexplicable lack of QProgressBar, but let’s not pick.

PS. Advertising

Since KDE4 is actually a real thing now, instead of just something that’ll happen in the future sometime, I don’t really have an excuse not to start writing things for it. So I am.

Holy crap.

I assumed it would be like Qt on steroids (that is, having features for everything you could possibly want), but seriously. KConfigDialog saves settings automatically. You just throw up a dialog, and all else is done.

It may be somewhat apparent that a login box is as far as I’ve got so far.

Anyway, what I’m trying to write is a client for http://pics.livejournal.com, because the current de facto Linux offering is a Perl upload-everything-in-a-directory script. No, really. I haven’t used it, so it may be surprisingly feature-complete, but we must have a GUI client or all the OS X fanbois will laugh at us.

Incidentally, the reason I have a single config box to show for a few hours’ work, other than coming in knowing next-to-nothing about KDE’s architecture, is because KConfigDialog kept asserting false (and SIGABRTing) and refusing to tell me why. #undefing QT_NO_DEBUG and, um, something similar from KDE didn’t make it tell me, so after traipsing through the API and source, I finally figured out it was because I called the submit URL ‘Server’ in the .ui file, and ‘Interface’ in the KConfig files. :suicide: