Re: What about VCard directory shared addressbooks?

Jose Medellin <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <[email protected]>
Extremely interested in what you said below..

Kevin Krammer <krammer <at> kde.org> writes:

> 
> On Tuesday, 2013-04-30, Henk van Velden wrote:
> > On Tuesday 30 April 2013 17:08:53 Kevin Krammer wrote:
> > > It mainly means that the program handling the directory won't
> > > automatically check for changes.
> > > I.e. if you change on of the files the data known to applications will
> > > still be the same and will be overwritten if any of those applications
> > > change the same contact.
> > > 
> > > In theory this could be handled very similar to how the maildir handler
> > > manages its directories, i.e. monitor for changes by other programs.
> > > Limited man power has so far not allowed to apply those enchan
> > > the vcard directory handler yet.
> > > 
> > > Cheers,
> > > Kevin
> > 
> > Thanks, this seems to be a rather to the point answer.
> > 
> > I understand from this that in our practical life, when I change an
> > address, my wife will not see this from her system immediatly, but after
> > stopping/starting Kontact (with normaly will be synchrone with a
> > logout/login at evening/morning). And when she during that session 
> > in the same vCard, my changes are lost.
> 
> I think you can also menually trigger reload of the addressbook.

How do I manually trigger the reload of the addressbook for Akonadi to 
read again the VCF File list?  Right clicking on the resource and clicking 
refresh doesn't do anything.  I heard somewhere that maybe a dbus 
message could be issued for the resource, but I have no idea how to 
even start with that.. If you point me in the right direction, I can look 
it up myself, no problem... I'm quite good with bash scripting know my
general way in programming.  This issue has become quite a nuisance
for me and it's the first time in 2 years I see a chance of fixing it!

> 
> > You also hint to the fact that this maybe solved in the future (without
> > time schedule).
> 
> Yeah. We actually discussed that at the latest PIM meeting, but neither of 
> main developers has currently time to look into that (either no time at all 
> busy with other areas) and new developers are hard to find when it comes to 
> backend work. Way to many "wow, look at this" development topics open in the 
> desktop application space.
> 
> Cheers,
> Kevin

Thanks!!

Jose


_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.