thank you very much for your personal involvement with the syncevolution project and the
response to me
You can copy-and-paste an existing backend (like akonadi), and then
rename files and classes as needed.
Thanks this was what I was planning to do, just needed a confirmation and clarification on
how it is done.
> May I ask for your opinion please - what would be the steps or send me
> web links to docs as I'm getting lost in the documentation?
Depending on the kind of PIM storage you need to interface with you need
to implement different interfaces. Most storages support
importing/exporting items in a standard format (like vCard or iCalendar)
and offer some kind of item listing. The TrackingSyncSource is a good
base class for this and comes with full documentation of all virtua
methods that one may have to implement.
TDE is the former KDE3 project. I'll need to have a look into the details on the
interfaces, but it looks possible.
> 1. Is there a way to sync with TDE without writing backends for TDE?
> I ask this in the bluetooth/usb context.
I don't know what kind of storage TDE supports. It's likely that you
will have to write a backend for its PIM API.
Thanks I had a look in the past days just to find out that new bluez5 works much different
(and perhaps better), but still could be the real challenge here.
> 2. Where do I start and what process should I follow to integrate the
> code into the build and in the gui?
Backends get detected automatically when placed in src/backends, so just
copy-and-paste, modify, then re-run autogen + configure + make.
Oh, thanks, however I have seen some checks and options to disable/enable KDE4+ and Gnome
linking in the code (I got from git).
So the question was more about how could I disable nearly everything else except for what
I want to test. Is there any (documented) process on how to modify or just hack the
> 3. In the backend part I see kde, kcalextended and akonadi for kde4 -
> why was that split up - I mean, I see what is in the code, but why the
kde is the platform support (KWallet). akonadi is the backend for PIM
storage via the Akonadi API. kcalextended is the backend for Nokia's
extended KCal calendar storage (as used in the N9).
Oh thanks. This is good as my final goal is to get the N9 syncing. I actually did a test
with gnome from Nokia 5530 and it worked pretty well.
Thanks again, it helped a lot get a better picture