Got (KDE) Shirts?
So, after searching for some cool KDE swag online and finding none (found some shirts and stickers of dubious quality at cafepress.com, but has anyone actually ordered anything from them and had good or bad experiences to share??), I found spreadshirt.com and tried their T-shirt designer thingey. After thoroughly enjoying watching their Flash-based designer crash Firefox about 10 times in a row (definition of insanity: doing the same thing over and over again, expecting different results), I admitted defeat and switched to my darling bride's Powerbook and Safari. Long story short, I custom-made 2 shirts (black, of course, is there any other shirt color?) and am now waiting eagerly for them to arrive.
Wrapping up the Summer of Code
I wrote this for this last week's commit digest and didn't want to steal Danny's thunder, but here's my thoughts on this year's SOC KPilot project...
KPilot progress(!!) and a fatal Plucker error
First, Bertjan is doing a wunderbar job with the keyring conduit in KPilot/trunk! I stayed up a bit last night and hacked for a while. Felt darned good. One annoyance that we've found, though, is that it looks like KWallet::Wallet (the KDE wallet subsystem) assumes that every program that wants to access the Wallet subsystem will have a top-level window. This assumption is not true with KPilot's syncing daemon (kpilotDaemon). So I've sent an e-mail off to kde-core-devel, and hope to hear something back on it soon, but does anyone in lazy-web-ville know what the Correct (TM) way is to work around this?
Um, yes, hi. I’m looking for Adriaan…
KPilot, She Progresses
Woohoo! I ate far too much cheesecake, far too late in the evening tonight, and therefore am still up at 2:30 a.m., hacking on KPilot. And oi(!) does it feel good. =:) We now have a working daemon, a working configuration window, a working kpilot main window, logging happening correctly over the DBus, and with the code that I'm about to commit to trunk, we now are able to get through a hotSync without crashing! W[][]t!
We are living in the science fiction we grew up with
I just got an e-mail from one of my best friends, who profoundly stated:
Good Morning, Vietnam^WPlanetKDE!
Greetings and salutations. And thanks to Chris for adding me to the planet. =:)
Visor Syncing Problems - A Solution
I've been trying to help a KPilot user (Hi Ronny!!) track down a really annoying and fatal bug for more than a year now. The bug is triggered by trying to sync a Visor handheld with KPilot, and what happens is that KPilot begins to connect to the Visor during a HotSync, but then it fails when trying to read the user information from the Visor; and then the Visor disconnects, but KPilot doesn't know it and KPilot then goes into a tight, CPU-consuming loop somewhere deep in the bowels of libpisock. Ronny graciously funded me with a Visor via eBay since I am unable to reproduce this condition with my Treo 650. Long story short, now that I have a Visor, I've been able to reproduce the bug, grr.
What Microsoft Meant Was…
In an effort to catch up reading through the last 2 months of eWeek magazines that I have stacked on my dresser yet never find time to pick up, I read through the May 28 issue this morning and found this very insightful statement by Jason Brooks. The article is called "Free software shines on" and can also be found here...
Why I quit: kernel developer Con Kolivas
Really, really good article and interview with an awesome and amazingly bright guy. Con, I had no idea that you were such a complex guy. I wish you the best of the future, seriously.