1:56 a.m.
Hi all,couple of years ago we discussed the advantages of syncevolution and SyncML over
opensync and support for KDE4.Back then I was not sure if I'll stick to KDE, but since
I preferred to stay on TDE for various reasons.
However I am missing one essential part - the sync with the mobile phone(s) in TDE, so I
was wondering what I can do about it, being already convinced that the only one could help
me is syncevolution.I would also write backends for TDE if necessary, as I already did for
opensync, but the integration of the code into the syncevolution build and gui are still a
mystery for me.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?1. Is there a way to sync with
TDE without writing backends for TDE? I ask this in the bluetooth/usb context.
2. Where do I start and what process should I follow to integrate the code into the build
and in the gui?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 split?
thanks in advance
regards
11:57 a.m.
On Wed, 2015-12-16 at 09:56 +0000, Emanoil Kotsev wrote:
Hi all,
couple of years ago we discussed the advantages of syncevolution and
SyncML over opensync and support for KDE4.
Back then I was not sure if I'll stick to KDE, but since I preferred
to stay on TDE for various reasons.
However I am missing one essential part - the sync with the mobile
phone(s) in TDE, so I was wondering what I can do about it, being
already convinced that the only one could help me is syncevolution.
I would also write backends for TDE if necessary, as I already did for
opensync, but the integration of the code into the syncevolution build
and gui are still a mystery for me.
You can copy-and-paste an existing backend (like akonadi), and then
rename files and classes as needed.
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.
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.
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.
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
split?
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).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12:45 p.m.
Hi Patrick,
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
automake files
> 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
> split?
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
regards
2:02 p.m.
On Mon, 2015-12-21 at 20:45 +0000, Emanoil Kotsev wrote:
>> 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.
I don't know how far back KCal goes, but perhaps at least that API is
similar.
>> 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.
SyncEvolution interfaces to Bluetooth via libopenobex, which talks
directly to the kernel. That part should work right away, also with
Bluez5.
>> 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 automake files
Once you ran autogen.sh, the resulting configure has enable/disable
options for all backends. There's no need to change the autotools source
files.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4:13 p.m.
> TDE is the former KDE3 project. I'll need to have a look into
the
> details on the interfaces, but it looks possible.
I don't know how far back KCal goes, but perhaps at least that API is
similar.
Well KCal might have not changed much, but in KDE4 akonadi provides a
unified interface afaik.Thanks again for the summary, I now have a much better
understanding what is there for what reason in syncevolution.
I think I'll find my way through that.
> >> 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.
SyncEvolution interfaces to Bluetooth via libopenobex, which talks
directly to the kernel. That part should work right away, also with
Bluez5.Yes indeed I was able to configure, pair and connect to the Nokia 5530 and N9 also
from within TDE using the gnome tools
The problem is that bluetooth was poorly
supported in KDE3, so I think if one aims to do the bluetooth part without gnome tools
could be chalinging. But it might be off topic here.
From what I recall from the opensync project the KDE3 did not have
unified API, but it shouldn't be hard to get working and I have never had issues on
that side.
> >> 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 automake files
Once you ran autogen.sh, the resulting configure has enable/disable
options for all backends. There's no need to change the autotools source
Ok
thanks, so it really adopts the backend specific features as provided by the am and
configure-sub.in files
thanks a lot, wish me luck
On Monday, December 21, 2015 11:02 PM, Patrick Ohly <patrick.ohly(a)intel.com>
wrote:
On Mon, 2015-12-21 at 20:45 +0000, Emanoil Kotsev wrote:
>> 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.
I don't know how far back KCal goes, but perhaps at least that API is
similar.
>> 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.
SyncEvolution interfaces to Bluetooth via libopenobex, which talks
directly to the kernel. That part should work right away, also with
Bluez5.
>> 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 automake files
Once you ran autogen.sh, the resulting configure has enable/disable
options for all backends. There's no need to change the autotools source
files.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9:56 a.m.
Hi again,
When I compile with --enable-shared my module comes up twice when I call
--datastore-properties ?When I compile static it shows up just once. I installed in
/tmp/test or ~/test-syncevo and setup some variables.
What could be the reason?
thanks in advance - regards
On Tuesday, December 22, 2015 1:13 AM, Emanoil Kotsev <deloptes(a)yahoo.com>
wrote:
> TDE is the former KDE3 project. I'll need to have a look into
the
> details on the interfaces, but it looks possible.
I don't know how far back KCal goes, but perhaps at least that API is
similar.
Well KCal might have not changed much, but in KDE4 akonadi provides a
unified interface afaik.Thanks again for the summary, I now have a much better
understanding what is there for what reason in syncevolution.
I think I'll find my way through that.
> >> 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.
SyncEvolution interfaces to Bluetooth via libopenobex, which talks
directly to the kernel. That part should work right away, also with
Bluez5.Yes indeed I was able to configure, pair and connect to the Nokia 5530 and N9 also
from within TDE using the gnome tools
The problem is that bluetooth was poorly
supported in KDE3, so I think if one aims to do the bluetooth part without gnome tools
could be chalinging. But it might be off topic here.
From what I recall from the opensync project the KDE3 did not have
unified API, but it shouldn't be hard to get working and I have never had issues on
that side.
> >> 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 automake files
Once you ran autogen.sh, the resulting configure has enable/disable
options for all backends. There's no need to change the autotools source
Ok
thanks, so it really adopts the backend specific features as provided by the am and
configure-sub.in files
thanks a lot, wish me luck
On Monday, December 21, 2015 11:02 PM, Patrick Ohly <patrick.ohly(a)intel.com>
wrote:
On Mon, 2015-12-21 at 20:45 +0000, Emanoil Kotsev wrote:
>> 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.
I don't know how far back KCal goes, but perhaps at least that API is
similar.
>> 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.
SyncEvolution interfaces to Bluetooth via libopenobex, which talks
directly to the kernel. That part should work right away, also with
Bluez5.
>> 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 automake files
Once you ran autogen.sh, the resulting configure has enable/disable
options for all backends. There's no need to change the autotools source
files.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
11:46 a.m.
On Thu, 2016-01-28 at 17:56 +0000, Emanoil Kotsev wrote:
Hi again,
When I compile with --enable-shared my module comes up twice when I
call --datastore-properties ?
Can you show the output?
Also check "syncevolution --version". It has some information about
loaded modules.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12:11 p.m.
Patrick,thanks for replying!
So here is what I see when I build "shared" ("statics" - I see only
one desc of the module)
Currently active::
CalDAV
...
TDE PIM Address Book = TDE PIM Contacts = addressbook = contacts = tdepim-contacts
...
TDE PIM Address Book = TDE PIM Contacts = addressbook = contacts = tdepim-contacts
...
TDE PIM Calendar = calendar = events = tdepim-events
...
TDE PIM Task List = TDE Tasks = todo = tasks = tdepim-tasks
...
TDE PIM Memos = memo = memos = tdepim-memos
...
TDE PIM Calendar = calendar = events = tdepim-events
...
TDE PIM Task List = TDE Tasks = todo = tasks = tdepim-tasks
...
TDE PIM Memos = memo = memos = tdepim-memos
...
bin/syncevolution --version
SyncEvolution 1.5.1
Loading backend library /tmp/test/lib/syncevolution/backends/syncxmlrpc.so
Loading backend library /tmp/test/lib/syncevolution/backends/synctdepimcal.so
<<<< my cal module
Loading backend library /tmp/test/lib/syncevolution/backends/synctdepimabc.so
<<<< my address book module
Loading backend library /tmp/test/lib/syncevolution/backends/syncsqlite.so
...
Loading backend library /tmp/test/lib/syncevolution/backends/syncdav.so
Loading backend library /tmp/test/lib/syncevolution/backends/syncakonadi.so
Loading backend library /tmp/test/lib/syncevolution/backends/syncactivesync.so
Loading backend library /tmp/test/lib/syncevolution/backends/providergoa.so
Loading backend library /tmp/test/lib/syncevolution/backends/platformkde.so
Loading backend library /tmp/test/lib/syncevolution/backends/platformgnome.so
Thanks
On Thursday, January 28, 2016 8:46 PM, Patrick Ohly <patrick.ohly(a)intel.com>
wrote:
On Thu, 2016-01-28 at 17:56 +0000, Emanoil Kotsev wrote:
Hi again,
When I compile with --enable-shared my module comes up twice when I
call --datastore-properties ?
Can you show the output?
Also check "syncevolution --version". It has some information about
loaded modules.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
1484
days inactive
1527
days old
syncevolution@synevolution.org
7 comments
2 participants
participants (2)
-
Emanoil Kotsev -
Patrick Ohly