Shrook now multi-threaded
I'm in the process of solving some of the tougher problems with Shrook, and I've just got one of the most long-standing ones out of the way, which is how unresponsive it is when checking for new items. The obvious answer was to split off the heavier work into a separate thread so the main UI thread isn't blocked by non-UI processing. It's a lot harder than it sounds, but as of today it's done. Shrook is now 100% usable during the process.The work for this also made it easy for me to batch together when new items appear, so the window content is no longer in a state of constant flux. You now get one big update every few seconds. I'll get this in your hands shortly.
Sorry for the lack of updates recently - I started a new day job a couple of months ago and it's taken a while for things to settle down. I've also wasted a lot of time looking into what Core Data can do for Shrook (A: Nothing. It could certainly replace a lot of the existing internals of Shrook, but wouldn't offer much new and has several enormous flaws. Most of the hype about it is simply not true).
-- Graham, August 5th, 2007 9:55 PM.
Answers
Thank you. Can't wait to use it, that should relieve quite a lot of pain for me.-- shane, August 10th, 2007 12:05 AM.
Fantastic news, on both counts. The performance issue has been really keeping me from running Shrook lately. And I've yet to see anything that used Core Data which impressed me. One of the beauties of Shrook is that you can dig in via the filesystem and open up the saved/cached posts.-- eric, August 14th, 2007 5:05 PM.