Sam, I recommend a tiny rethink about your problem. I see two issues. Populating the sqlite db is one and display it is another. Why use one process to do both?
Ruby thread goodness (or lack of) is a bit of unwarranted FUD. If you look hard enough, my name is on some of that old wxWindows code.I know where it came from and threads and mulit-core weren't an issue back then. Handling asynchronous events that have nothing to do with with GUI widgets or mouse clicks or keypress, those were wild dreams, Back then, there were no events to handle in a GUI framework other than GUI related events. So, we got timers IF the OS had them (back then it was iffy they would work cross platform at the millisecond tick rate) I gather "a wing and prayer" then is a promise now. I'm not saying Shoes doesn't have some refresh issues or thread funkiness that I don't understand but It's not pretending to be WxWindows or TK or XVT or the Star Division library thing. Pretty cool that it works cross platform as is. A modern day Ruby Hypercard (just needs a few "on" handlers). If you look at the C and the #ifdef's you'd worry it'll bloat beyond comprehension for all the special cases folks want it handle. It's still understandable (barelt) Off the soapbox now. Sorry to bend your ears. --Cecil
