On Sunday, 1 June 2014 15:46:44 CEST, Dan Chapman wrote:
Although this makes the use of the API's in the same kind of way as the
desktop gui
Definitely not like this. I do *not* want to duplicate the same business
logic in the DesktopGui and in the Ubuntu version. I want a single
component wr
On Thursday, 5 June 2014 08:39:58 CEST, Kevin Krammer wrote:
class Composer : public QObject
{
Q_OBJECT
Q_PROPERTY(QString identity )
Q_PROPERTY(ReceiverModel toModel CONSTANT)
Q_PROPERTY(ReceiverModel ccModel CONSTANT)
Q_PROPERTY(ReceiverModel bccModel ... CONST
On Wednesday, 4 June 2014 23:58:25 CEST, Steve Dodd wrote:
Maybe the back off is the way to go then - unfortunately AIUI
imap errors aren't nicely coded in the same way that SMTP errors
are, so there's no chance to be smart and behave differently in
response to different situations...
I would
On Saturday, 2014-06-07, 14:26:49, Jan Kundrát wrote:
> One thing which I'm unsure about is splitting the concept of recipients
> into three parts (To, Cc, Bcc). Maybe it would make more sense to use a
> two-column model, first column tracking the type of the recipient
> (to/cc/bcc), the other col
