[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] kpilot and kaddressbook
From:       Adriaan de Groot <groot () kde ! org>
Date:       2006-06-13 10:20:47
Message-ID: 200606131220.48039.groot () kde ! org
[Download RAW message or body]

[[ Right, this time with actual content. ]]

On Tuesday 13 June 2006 10:51, Mads Bondo Dydensborg wrote:
> Tirsdag den 13. juni 2006 09:52 skrev Adriaan de Groot:
> > Until someone steps up and says "I *really* want this feature and am
> > going to hack C++ until it is there," this is likely to remain like that.
>
> Do you have any refs to documentation about the difference?

Get kpilot's SVN (several MB download):

svn co https://cvs.codeyard.net/svn/kpilot

That has a trunk/ which is the current development branch. The directory 
trunk/lib/pilot-link-0.12 contains a not-yet-released CVS version of 
pilot-link, the underlying library, which is what KPilot now uses and which 
theoretically has support for newer stuff.

The file pi-contact.h (vs. pi-address.h) has the API and the structure 
documentation.

That's the low-level underlying stuff. At a higher level, you will want to be 
in trunk/lib/, looking most at pilotAddress.{h,cc} -- I don't think that 
forking is needed at that level, if we do it carefully.


> What should make it so complicated? Are the two formats very different?

It's not so much complicated as really tedious; once the other fields are 
pulled out of the database, they need to be processed. That touches a fair 
number of the parts of the code -- the address book conduit to start with. A 
start would be just dumping the contacts. To do that, you would have to 
modify the address conduit to accept either the address or the contact DB.



-- 
Adriaan de Groot
  KDE Quality Team
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
[prev in list] [next in list] [prev in thread] [next in thread]