Having just submitted my first patch, I feel entitled to gripe and moan about certain aspects of Sup. The hope is that I'll get some pointers on what code to look at to fix these gripes. These gripes are independent of the hanging/other behavior in my other monster thread. (I'd say the asynchronous polling hang is my other biggest gripe, but that's not an issue for here).
1. Threads should be lazy-loaded (possibly in the background), with visible messages first. If a conversation got a new message, Sup should only take its time to load that message, and not the frickin' 24 other messages that were also incidentally there. I suspect this will require some pretty major refactoring. As a stop-gap, I should have the option of cancelling when I open a long thread (right now, I think it causes sup to crash). 2. Auto-completion sucks and should be improved. I should be able to press "c", type two letters, and then mash tab. If auto-completion actually works, then I'll blame it on dismal contacts.txt support (if I send mail to someone, there should be a configuration twiddle that saves it to contacts.txt. And then remembers it the next time I want to compose mail to them). 3. Polling and loading of threads should started, asynchronously, at the same time. Loading of threads should not hose my CPU. Loading of threads should do smart things, instead of doing an O(n) time warp. It takes forever for a mail from two months ago that is still in my inbox, because it still hasn't been addressed, to show up. This could probably be fixed with a cache file. This isn't as big of a deal if asynchronous polling hang and crashing is fixed. 4. Sup should prompt me whether or not I want to Reply All or Reply on appropriate cases, like pine. Cheers, Edward _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
