Tony Meyer wrote: >> I'd like to get a tab added to the Manager for configuring >> the notification sounds. It may be just edit boxes for the >> filenames at first (no browse), but I think we need something >> if general users are going to be able to take advantage of it. > > +1. Browse shouldn't be too hard - you should be able to just call > CreateFileDialog, right?
Unfortunately, that's kind of the sticking point. CreateFileDialog comes from win32ui, not win32gui, and win32ui requires the MFC dlls. After all the work that was going on around the time I joined the project to eliminate the need for win32ui, I hate to add it all back just for one options page. >> Given that we haven't been able to solve the bsddb >> corruption/run-recovery problem, > > I've completely given up and am happy in my ZODB.FileStorage world > <0.1 wink>. I'd like to include the necessary ZODB stuff in a a1 > build so that people can give ZODB a go if they would like, assuming > that it doesn't bloat the installer too much. I played around a little with a SQLite classifier also, which is very lightweight to install. It was pretty slow when working with the 2.8 version because of the way we do our commits, but I'd like to give it another go with the 3.0 version of SQLite to see if the situation has improved. Maybe I can get this in for 1.1a2 so that it could get some testing. Right now, I don't know if it would really be any more stable than bsd or not. >> I wanted to try something >> with automatic backups to at least provide a recovery >> mechanism. My idea was to detect if the database is still >> good when shutting down, > > How? Back when I was playing with things (and I think Richie found > this too, but it's a long time back) I found that you could corrupt > the database and the RUN_RECOVERY error wouldn't be triggered until > several accesses later. That could definitely be a problem. It's still just an idea at this point, so figuring out how to make it work is still a ways off. <wink> My idea was to check only when shutting down, so unless the corruption was caused by the shutdown itself we would probably be OK. It should, at the very least, significantly reduce the window for total loss of training data. >> and if so make a backup copy of the >> .db file. When starting up, if the training data is corrupt >> then try to restore this "known good" backup and then attempt >> the open again. > > Making a backup could be worth a go, though. Maybe this ought to be > an (Outlook experimental) option? It will almost double the amount > of disk space that the plug-in requires. Yeah, I definitely want to make it optional. It not only increases the disk space, but also increases the time it takes to shut down. -- Kenny Pitt _______________________________________________ spambayes-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/spambayes-dev
