<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1453928007741_30015">Hi again,</div><br><div id="yui_3_16_0_1_1453928007741_34902">When I compile with --enable-shared my module comes up twice when I call --datastore-properties ?</div><div id="yui_3_16_0_1_1453928007741_34931">When I compile static it shows up just once. I installed in /tmp/test or ~/test-syncevo and setup some variables.</div><div id="yui_3_16_0_1_1453928007741_34932"><br></div><div id="yui_3_16_0_1_1453928007741_30338" dir="ltr">What could be the reason?</div><div id="yui_3_16_0_1_1453928007741_34933" dir="ltr"><br></div><div dir="ltr">thanks in advance - regards<br></div><div id="yui_3_16_0_1_1453928007741_29967"><span></span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font face="Arial" size="2"> On Tuesday, December 22, 2015 1:13 AM, Emanoil Kotsev <deloptes@yahoo.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv8508541843"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;">>> TDE is the former KDE3 project. I'll need to have a look into the<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116125" clear="none">>> details on the interfaces, but it looks possible.<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116127" clear="none">><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116129" clear="none">>I don't know how far back KCal goes, but perhaps at least that API is<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116131" clear="none"><div id="yiv8508541843yui_3_16_0_1_1450713582374_116247">>similar.</div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116528"><br clear="none"></div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116529">Well KCal might have not changed much, but in KDE4 akonadi provides a unified interface afaik.</div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116530">Thanks again for the summary, I now have a much better understanding what is there for what reason in syncevolution.<br clear="none"></div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_116531">I think I'll find my way through that.</div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_116532"><br clear="none"></div>><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116135" clear="none">>> >> 1. Is there a way to sync with TDE without writing backends for TDE?<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116137" clear="none">>> >> I ask this in the bluetooth/usb context.<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116139" clear="none">>> ><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116141" clear="none">>> >I don't know what kind of storage TDE supports. It's likely that you<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116143" clear="none">>> >will have to write a backend for its PIM API.<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116145" clear="none">>><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116147" clear="none">>> Thanks I had a look in the past days just to find out that new bluez5<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116149" clear="none">>> works much different (and perhaps better), but still could be the real<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116151" clear="none">>> challenge here.<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116153" clear="none">><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116155" clear="none">>SyncEvolution interfaces to Bluetooth via libopenobex, which talks<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116157" clear="none">>directly to the kernel. That part should work right away, also with<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116159" clear="none"><div id="yiv8508541843yui_3_16_0_1_1450713582374_116833">>Bluez5.</div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116834">Yes indeed I was able to configure, pair and connect to the Nokia 5530 and N9 also from within TDE using the gnome tools<br clear="none"></div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116835">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.<br clear="none"></div><div id="yiv8508541843yui_3_16_0_1_1450713582374_116836"><br clear="none"></div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_117187">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.<br clear="none"></div><div id="yiv8508541843yui_3_16_0_1_1450713582374_117186"><br clear="none"></div>><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116163" clear="none">>> >> 2. Where do I start and what process should I follow to integrate the<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116165" clear="none">>> >> code into the build and in the gui?<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116167" clear="none">>> ><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116169" clear="none">>> >Backends get detected automatically when placed in src/backends, so just<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116171" clear="none">>> >copy-and-paste, modify, then re-run autogen + configure + make.<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116173" clear="none">>><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116175" clear="none">>> Oh, thanks, however I have seen some checks and options to<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116177" clear="none">>> disable/enable KDE4+ and Gnome linking in the code (I got from git).<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116179" clear="none">>> So the question was more about how could I disable nearly everything<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116181" clear="none">>> else except for what I want to test. Is there any (documented) process<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116183" clear="none">>> on how to modify or just hack the automake files<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116185" clear="none">><br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116187" clear="none">>Once you ran autogen.sh, the resulting configure has enable/disable<br class="yiv8508541843" id="yiv8508541843yui_3_16_0_1_1450713582374_116189" clear="none"><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_117116">>options for all backends. There's no need to change the autotools source</div><div id="yiv8508541843yui_3_16_0_1_1450713582374_117117"><br clear="none"><span></span></div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_117119"><span id="yiv8508541843yui_3_16_0_1_1450713582374_117118">Ok thanks, so it really adopts the backend specific features as provided by the am and configure-sub.in files</span></div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_117122"><br clear="none"><span id="yiv8508541843yui_3_16_0_1_1450713582374_117118"></span></div><div dir="ltr" id="yiv8508541843yui_3_16_0_1_1450713582374_117448"><span id="yiv8508541843yui_3_16_0_1_1450713582374_117118">thanks a lot, wish me luck</span></div> <div class="yiv8508541843qtdSeparateBR"><br clear="none"><br clear="none"></div><div class="yiv8508541843yqt6677049035" id="yiv8508541843yqt65966"><div class="yiv8508541843yahoo_quoted" style="display:block;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"><font face="Arial" size="2"> On Monday, December 21, 2015 11:02 PM, Patrick Ohly <patrick.ohly@intel.com> wrote:<br clear="none"></font></div> <br clear="none"><br clear="none"> <div class="yiv8508541843y_msg_container">On Mon, 2015-12-21 at 20:45 +0000, Emanoil Kotsev wrote:<br clear="none">> >> May I ask for your opinion please - what would be the steps or send me<br clear="none">> >> web links to docs as I'm getting lost in the documentation?<br clear="none">> ><br clear="none">> >Depending on the kind of PIM storage you need to interface with you need<br clear="none">> >to implement different interfaces. Most storages support<br clear="none">> >importing/exporting items in a standard format (like vCard or iCalendar)<br clear="none">> >and offer some kind of item listing. The TrackingSyncSource is a good<br clear="none">> >base class for this and comes with full documentation of all virtua<br clear="none">> >methods that one may have to implement.<br clear="none">> <br clear="none">> TDE is the former KDE3 project. I'll need to have a look into the<br clear="none">> details on the interfaces, but it looks possible.<br clear="none"><br clear="none">I don't know how far back KCal goes, but perhaps at least that API is<br clear="none">similar.<br clear="none"><br clear="none">> >> 1. Is there a way to sync with TDE without writing backends for TDE?<br clear="none">> >> I ask this in the bluetooth/usb context.<br clear="none">> ><br clear="none">> >I don't know what kind of storage TDE supports. It's likely that you<br clear="none">> >will have to write a backend for its PIM API.<br clear="none">> <br clear="none">> Thanks I had a look in the past days just to find out that new bluez5<br clear="none">> works much different (and perhaps better), but still could be the real<br clear="none">> challenge here.<br clear="none"><br clear="none">SyncEvolution interfaces to Bluetooth via libopenobex, which talks<br clear="none">directly to the kernel. That part should work right away, also with<br clear="none">Bluez5.<br clear="none"><br clear="none">> >> 2. Where do I start and what process should I follow to integrate the<br clear="none">> >> code into the build and in the gui?<br clear="none">> ><br clear="none">> >Backends get detected automatically when placed in src/backends, so just<br clear="none">> >copy-and-paste, modify, then re-run autogen + configure + make.<br clear="none">> <br clear="none">> Oh, thanks, however I have seen some checks and options to<br clear="none">> disable/enable KDE4+ and Gnome linking in the code (I got from git).<br clear="none">> So the question was more about how could I disable nearly everything<br clear="none">> else except for what I want to test. Is there any (documented) process<br clear="none">> on how to modify or just hack the automake files<br clear="none"><br clear="none">Once you ran autogen.sh, the resulting configure has enable/disable<br clear="none">options for all backends. There's no need to change the autotools source<div class="yiv8508541843yqt1458592274" id="yiv8508541843yqtfd80230"><br clear="none">files.</div><br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Best Regards, Patrick Ohly<br clear="none"><br clear="none">The content of this message is my personal opinion only and although<br clear="none">I am an employee of Intel, the statements I make here in no way<br clear="none">represent Intel's position on the issue, nor am I authorized to speak<br clear="none">on behalf of Intel on this matter.<div class="yiv8508541843yqt1458592274" id="yiv8508541843yqtfd58204"><br clear="none"><br clear="none"><br clear="none"><br clear="none"></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>