[Konversation-devel] [konversation] [Bug 318510] Modernize system contacts integration to properly support Akonadi resources and Nepomuk

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=318510

Eike Hein <hein at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Address book contact        |Modernize system contacts
                   |enumeration not working     |integration to properly
                   |                            |support Akonadi resources
                   |                            |and Nepomuk
           Severity|normal                      |wishlist

--- Comment #2 from Eike Hein <hein at kde.org> ---
Testing this again, the above appears to be true in some sense.

When creating a new contact via Konversation, it is added to std.vcf in
$KDEHOME/share/apps/kabc (where $KDEHOME is ~/.kde or ~/.kde4 depending on
distro), which is the classic contact storage location for KAddressBook. It's
possible to add this .vcf file as a new address book resource to Akonadi,
either via File -> New -> Add Address Book in KAddressBook, or via the Akonadi
Configuration section in System Settings. Pick the "VCard File" resource type
and navigate to std.vcf, then enable the new address book in KAddressBook.

Akonadi and KDE by default don't seem to set up any address book resources, but
I assume a user setting up their first address book would probably use the
"Personal Contacts" resource these days rather than intuitively above. If
std.vcf already exists by the time Akonadi is first used, the automatic
first-run Resource Migrator would presumably find and import it, however.

As such, this isn't really a bug - it's possible to make Konversation and
Akonadi talk to each other by setting up the right resource in Akonadi.
However, it would be better if Konversation were more flexible and would e.g.
allow the user to select the address book resources to consider, instead of
using the outdated classic kdepimlibs API which is locked into operating on
std.vcf. As mentioned we're aware of this requirement and plan to address this
by porting to kpeople in the future.

I'm going to keep this open, but rename it and reclassify it as a wishlist
item, to serve as a ticket to track progress on this porting work.

-- 
You are receiving this mail because:
You are the assignee for the bug.