Initially, I was skeptical about the design, but it’s actually a pretty nice little tool. When someone wants to borrow a browser, being able to just hit guest, let them play on their own desktop, log them out, and return to what you were doing, is very handy.
So I upgraded to ext4 with jaunty on my desktop lately. I needed the 2.6.28 kernel to get my tv card (hvr-3000) working, and since ext4dev had been retagged as ext4, it seemed a good time.
All in all, ext4 has been nice so far, but over about three weeks of use, I’ve gotten “no [...]
I received an SVGSlice bug report today. I haven’t actually looked at SVGSlice in ages.
So I’ve just posted SVGSlice 0.15 to launchpad. Mostly it just updates the code to work with a SAX namespace change (sax.saxutils.DefaultHandler -> sax.handler.ContentHandler), and does a few other small anti-bitrot cleanups. Unfortunately there’s a bug in Jaunty’s [...]
Scott posted that Git sucks, citing the yak-shaving necessary just to push a branch to another host for publication, and the horrible documentation that doesn’t actually explain the most basic things, except using Git’s own internal jargon. I have to agree with him. I got over all that though, and used it a fair bit, mostly because I loved the speed of Git. There are some things one just can’t get over so easily though, namely having your work hosed.
Alexander Larsson has posted about Removing flicker from GTK+ using client-side windows. It all sounds great, as far as it goes. I’m just wondering what this means for accessibility though. My understanding was that a lot of accessibility APIs require the formal window definitions to identify widgets etc. Maybe that’s just [...]
Continue reading about GTK+ client-side windows and accessibility?
