Last few days together with Murray I have been working on for example the status infrastructure in the Tinymail framework.
We simplified how to internally deal with status callbacks, we made sure that they’ll happen in the right order and wont happen after the final callback happened.
I created two video demos this time. A first one is for most people. It will show you how much status you can get out of the framework in case you will create a client on top of Tinymail. The video shows you the demo user interface with its ‘glamorous’ :-) progress bar (which shows a lot more status than “some other” E-mail client’s progress user interface).
User video demo, Rescaled one on youtube
A second is a technical video demo for people who want to learn how Tinymail works. Although it’s mentioned, it doesn’t really try to illustrate how to use the API to for example update a progress bar and show a status bar. The technical video demo shows you how Tinymail deals with launching status callbacks internally.
I did the technical one with a normal video camera. That’s why the quality isn’t ideal. After doing that one, while not being satisfied, I discovered xvidcap for making the user video demo. Its quality is excellent. Therefore I recommend xvidcap for screencasting and I’m probably going to use this tool more often indeed. Finally I use Cinelerra to glue audio to it, cut and paste the “eums”, “swallow” and “grrmm”s away.
I will immediately write it here: whether or not this support for status in the IMAP code of Tinymail can go upstream to Evolution’s Camel. depends on the willingness of the Evolution team to start accepting patches that would synchronize camel-lite with Camel.
These status changes depend on other changes: a few months ago (more than six months now, I think), I removed a temporary memory buffer from the IMAP code. The current version for Tinymail writes the E-mail immediately while reading from the socket to the filesystem cache. It’s in the middle of that total rewritten code that this status support code had to be put.
This is your technical reason why you are not seeing a patch on the Evolution mailing list: what use is that patch if that previous patch isn’t processed yet?
Matthew Barnes as been working on getting some of my stuff back into Evolution. This is great, of course. You can aid him (and me) to speed such things up. That would be much more productive than wining about it!
Oh. I saw the “From”-label bug too. That one is already fixed indeed.