Talk:Projects/xomail

I think your understanding of Tinymail is flawed. Tinymail is mostly a set of back-end tools for constructing a front-end, not really a working client. The default client probably would work on Sugar, but to my knowledge no-one has done the work to install it and get it running (significantly, the compile options for "OLPC" and those for include-python-bindings are separate, which makes me wonder what "OLPC" means); thus it would be stretching the truth to call it "working". I have never programmed an email client, but I would imagine that, between the pain of learning to use a toolkit which already has python bindings (tinymail) and the pain of making a compatible email client from scratch, you'd probably be better off with the former. Email has been around for decades and the important protocols are definitely more byzantine than they should be. And yes, just put it in whatever box tinymail gives you, all flat, and do the index of tags yourself.

Certainly, it would be worth evaluating tinymail as opposed to python's standard libraries.

But feel free to ignore me, that is just my opinion.

Homunq 17:15, 1 April 2008 (EDT)

Hi Homunq, thanks for the feedback. No, actually, I do know that Tinymail is only a framework - in 'Background' I meant to refer more to the demo client. I will clarify the wording on the page. :-) :An alternative user interface is definitely possible. Let me explain my reasoning for not really considering Tinymail. I think it's overkill. Really! Downloading all email from a POP connection can be done in a few lines of code with Python. MIME-parsing is slightly more involved but I would expect the same or worse with Tinymail's MIME handling methods. So if I've made the point for using Python standard libraries and not Tinymail, using Tinymail for just storage in mbox/maildir/mh does not make sense. Database storage is also less pain and makes more sense for my goals for this activity though it has to be done right. Shikhar 05:54, 2 April 2008 (EDT)