Current project: Picross in Ruby, using Korundum and such. Which is so much better than using C++ directly. <3

However, note to me and anyone else using it: Qt::MainWindow#central_widget= doesn’t work. You have to use #setCentralWidget or #set_central_widget, or whatever, otherwise it’ll overlap with the other parts of the window like the menu bar and so on. Knowing this in advance would’ve saved about an hour of futile debugging. (Obviously this goes for KDE::MainWindow and KDE::XmlGuiWindow as well.)

On the other hand, the fact that it automatically translates ruby_style_identifiers to qtStyleIdentifiers is pretty cool, even though I suppose in the grand scheme of things it’s about as important as bracketing styles…

Update: some screenshots to show what I mean.

set_central_widget	central_widget=
Good	Arg

This is why Qt is the best toolkit ever. Shame the Kubuntu repos still only have 4.3. (I know I could update it myself, but that will invariably prove to be a pain in the bum somewhere down the line.)

For some reason I never really connected MapReduce with futures in my mind until just now, but yes. Everyone knows the real name for reduce is foldl, though. :v

I’m certain no-one cares, but, KScrapbook is now as abandoned as Fotobilder is. I should have noticed this with the LiveJournal/Photobucket integration, to be honest. Anyway, I didn’t really see the point in continuing.

In fairness, Fotobilder’s not really abandoned as much as just being folded into LiveJournal. But if they can’t be bothered to update their documentation, well, I’m a bit stuck either way.

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: