[Kde-pim] Mailreader status and RFC

[Tom Albers]

Op Thursday 10 September 2009 12:48 schreef u:
> > 1) Where to put the code? The possibilites are: libkdepim, kdepimlibs or
> > remains where it is in kdepim. I think the best would be to move to
> > kdepimlibs in mid-term, but see 2).
> 
> This question is also relevant for the other parts ripped out of KMail, like 
> the message composer, the message list and eventually the template stuff.
> The message composer is generic enough to be useful for other applications and 
> can therefore be moved to kdepimlibs, while the message list and the template 
> stuff are too specific.
> I am not sure about the mailreader. Tom, do you think it would be useful for 
> Mailody?

I've choosen to use qtwebkit to view messages, as most html mails are broken and webkit seems to deal better with it. I'm not prepared to switch back. I do think it adds value to do it in kdepimlibs.

libkdepim is evil and nothing should be added there imho.

Also I split the view of the headers from the message body for security reasons. I don't want to give the body any chance to manipulate the header view. So unless that's too in this lib that's another reason for Mailody to not use it. 


> I think the decision was to allow GPL licensed code in kdepimlibs, as 
> eventually we might want to move libkleo there. The mailreader even depends on 
> libkleo. Re-licensing libkleo to LGPL was not an option, therefore mailreader 
> has to be GPL too.

Yes. Put it in as GPL. That way evil companies can not incorporate the code in closed source applications. So I'm all for GPL libs.

> > Thanks for reading,
> Thanks for coding :)

+1. I think it gives the oppertunity for more mail specialised mail clients, which would be a positive development.

Best.

Toma
-- 
KDE Developer
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/