[prev in list] [next in list] [prev in thread] [next in thread]
List: kmail-devel
Subject: Kontact: KMail/KOrganizer integration
From: Bo Thorsen <bo () sonofthor ! dk>
Date: 2003-03-31 19:11:20
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I'm starting on the KOrganizer kroupware_branch merge now. There's an
initial question that needs answering: Where to put the KOrganizer
specific DCOP stuff.
Right now, there is a KMail part interface (used by Kontact), a KMail iCal
interface (used by the libkcal IMAP resource) and some more. KOrganizer
needs access to a bunch of different DCOP methods too, and I'm
considering wether or not to make a new interface for that one.
Alternatively, I think the best would be to put it in the iCal interface
that Steffen made for the resources. It would definately not fit in the
Kontact (the part) interface, since it will be possible to do the
KMail/KOrganizer workings with the separate applications.
I would prefer, though, to make a new interface for the KMail/KOrganizer
integration. This would more cleanly separate the functionality from the
others. The iCal interface currently only handles storing libkcal
calendars in KMail (and I'm considering a name change of that interface
to kmailresourceIface) and I would prefer to keep it this way.
To have a place to start the coding in, I'll go with kmailicalIface right
now. But if the crowd agrees, what would be good names for the
interfaces?
Bo.
- --
Bo Thorsen | Praestevejen 4
Senior Software Engineer | 5290 Marslev
Klarälvdalens Datakonsult | Denmark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+iJLYmT99lwfUS5IRAkbOAKDLJZDgCQ0Ks4Y46UlTQcH+9hC+IgCgmTRl
2JIW+RS3cra9nfdeuYi9dgw=
=wYTZ
-----END PGP SIGNATURE-----
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic