On Wed, 5 Jun 2013, Jan Kundr?t wrote:
On Wednesday, 5 June 2013 15:53:32 CEST, Pali Roh?r wrote:
2) Create qt library plugin(s) with KDE API which can be called
from Trojita at runtime - if plugin(s) will be available
I prefer this one. In my opinion, this will make it much easier for packagers
(think "trojita" and "trojita-integration-kde"), enforce a strict separation
of tasks on the API boundary, and make it straightforward to add independent
implmentations of similar funcitonality with other DEs in future.
I'm also interested in what the others think here.
Something along these lines sounds like the right approach.
For components that require much tighter integration into KDE (akondi for
example), create a separate process that ties into KDE and have Trojita talk to
it through some sort of API (bonus points if the existing address book work can
get converted to use the new API so that it's proof that the API can be used for
multiple destinations)
It's good to get Trojita able to leverage more stuff that exists, but you want
to avoid having to pull in a lot of KDE libraries and daemons if you just want
to use Trojita on a system that doesn't have KDE on it.
David Lang
