Quote:
Originally Posted by hawhill
So now you know why all the fancy apps here - with the notable exception of KUAL - do not use the Kindlet framework :-)
|
Hah, yeah. It's kind of a bitch to work with. I don't really feel like deploying over ssh every time I want to test my app, but maybe that's just my workflow*. In any case, probably won't be doing much with e-ink until a better platform comes around.
For posterity, I've dumped the source code into a zip and attached it to this post. Still haven't nailed down the bad thread exit, but with debug tools being what they are (functionally nonexistent), it doesn't really feel worthwhile to try and track down something that will only affect me when the app closes - which, since I'm using it as an actual clock, will end up being not very often.
*Come to think of it, it wouldn't be that much worse than signing the jar every time, which I automated with a batch file. Still.