kde-common/accounts in kmail's addressbook
carpdjih at sp.zrz.tu-berlin.de
Tue Jun 4 17:17:08 BST 2002
-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday 04 June 2002 20:15, Marc Mutz wrote:
> I want to see how you want to maintain stable "external" interfaces if
> the whole message handling core is exchanged in the app. ;-)
For one thing: you don't need to have just one single interface. You can add
as many as you like (so provide those that are not going to change for now).
Second: don't provide access to internal datastructures. Provide interfaces
with the fucntionality you can offer now (so changing the implementation
doesn't do any harm).
You need two things in the interfaces:
1) events that plugins react on (i.e. "composerOpened", giving access to the
composer interface, or "messageOpened", giving access to the opened message.
2) some sort of library to do something with the data, i.e. the mails. Just
offering a message as QString is nice for the beginning, but some methods for
accessing attachments or manipulating headers would be nice. Provide a small
interface around KMime for example, with the most common things that are
guaranteed to be available after any rewrite.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the kde-core-devel