[kdepim-users] KDE SC 4.4.0 and address book (solved)

[Art Alexion]

On Saturday 13 March 2010 16:39:52 you wrote:
> On Sunday 28 February 2010 06:49:14 Ingo Klöcker wrote:
> > I think you are a bit confused by all this new stuff and this is fully 
> > understandable for anybody who does not follow the development as 
> > closely as I do. I'll try to solve a bit of your confusion.
> >
> > 
> >
> > KDE SC 3.5 supported (via the KDE Resources framework) address books 
> > stored in many different ways, e.g.
> > - a vCard file
> > - a folder containing individual vCards (one per contact)
> > - on an IMAP server
> > - ...
> >
> > 
> >
> > Akonadi supports address books stored in (not yet many) different ways, 
> > e.g.
> > - a vCard file (via a native Akonadi resource)
> > - a folder containing individual vCards (one per contact) (via a native 
> > Akonadi resource)
> > - on an IMAP server (via the compatibility Akonadi resource)
> > - everything supported by the KDE Resources framework (via the 
> > compatibility Akonadi resource)
> >
> > 
> >
> > What does change with Akonadi?
> > For the developer: A lot. Akonadi is a whole new way to access PIM data.
> > For the users: Basically nothing. Maybe the terminology used in the 
> > applications will change a bit, but we try not to expose technical terms 
> > in the user interface.
> >
> > 
> >
> > In particular, what does not change with Akonadi is the actual storage. 
> > Akonadi is no storage. It is very often confused with a storage. But it 
> > is no storage. Akonadi is a layer between the storage (vCard file, 
> > folder with vCards, IMAP folder) and the applications.
> 
> This sheds some light on the problem that I just mentioned with kmail not 
> seeing the native resource.  It would appear that it is the "migrated"
> vCard  file that it isn't seeing.
> 
> Any suggestions on how to fix this?

I should add that I looked in Settings>Composer>Configure Completion Order, and 
only the native resource, not the compatibility resource, appears, but the 
data itself is only coming from the compatibility resource.

While my work-around is making things work fine for now, I would prefer to get 
it working correctly, instead.  Work-arounds tend to break with updates.


-- 
Art Alexion
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users