[Development] Proposal: "rebranding" QMF as QtMail

Robin Burchell robin+qt at viroteck.net
Mon Feb 17 12:25:44 CET 2014


Hi,

Sorry for the delay in replying.

On Mon, Feb 10, 2014 at 6:34 PM, Konstantin Ritt <ritt.ks at gmail.com> wrote:
>> QmfClient => QtMail
>> QmfMessageServer => QtMessageServer
> Two modules in one repo (aka QT += mail messageserver), right?

Yes. Same situation as it is now.

> BTW, are you planning an API review/refactoring for it?

I personally feel that some changes are in order (e.g. dropping the
custom logging solution in favour of category logging, but I'd like to
wait with that until Sailfish has moved to 5.2 in the
hopefully-not-too-distant-future); another thing I don't really like
is that protocol plugins define a UI for creating & editing accounts
(thus tying them to QtWidgets, and also being rather unnecessary given
that platform tie-in probably means not using the built-in UI anyway.
I'd like to separate those to an account configuration tool, I think,
somehow).

I should probably start creating JIRA items.

</ramble>

If you have proposals for other changes, I'm open to hearing about
them. In general, I don't think most of the usability of the API is a
problem apart from a few occasional trouble points, but different
perspectives are always interesting.

BR,
Robin



More information about the Development mailing list