Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread deloptes
Tone Kastlunger wrote: > I think it'd be important to add it next to bluez4 dbus stuff (and hence > straightforward perhaps). > > I mean, adding bluez5 next to bluez4 support *might* just be easier (i.e. > less changes) than moving to Y.A.L. Bluez4 is beeing removed, but yes this is what I mean

Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread Tone Kastlunger
>May be it is better using QDbus and not linking against kf5bluezqt and thus >making buteo-syncfw depend on this library for couple of operations >required to handle the sync profile. I think it'd be important to add it next to bluez4 dbus stuff (and hence straightforward perhaps). I mean, adding

Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread deloptes
Damien Caliste wrote: > What about buteo-syncfw ? May be it is better using QDbus and not linking against kf5bluezqt and thus making buteo-syncfw depend on this library for couple of operations required to handle the sync profile. I am still thinking about it and I'm not sure. Let me know what

Re: [SailfishDevel] SDK versioning

2019-07-26 Thread Tone Kastlunger
Who's talking about older sdks? On Thu, Jul 25, 2019 at 9:43 PM Андрей Кожевников wrote: > Why you need older sdk with bugs, when you can use latest sdk with > multiple targets for older sfos versions? > > чт, 25 июл. 2019 г., 20:39 Tone Kastlunger : > >> +1 to this; >> I had the same issue. It'

Re: [SailfishDevel] SyncML Plugin Server question

2019-07-26 Thread deloptes
Chris Adams wrote: > 3) it's worth checking `git blame ` to see which commit added > that #ifdef to try to see why it was done that way.  It may be incorrect. > If you trace the code, can you see any other such cases where the > reference count to a plugin process was not updated "appropriately"?

Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread deloptes
Chris Adams wrote: > It sounds like you're making good progress which is fantastic! > Please tag me in any merge requests (using @chriadam on github etc) so > that I get notified of them, and then I can review etc. > Yes indeed, it works perfectly well. There are still some open questions and bu

Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread deloptes
Damien Caliste wrote: > Can you point out where did you push your modifications to buteo stack ? > I would like to give a look and test. > > I guess that > https://git.sailfishos.org/deloptes/poc-bluez5-buteo-syncml-plugins is a > fork of buteo-sync-plugins with your changes. What about buteo-syn

Re: [SailfishDevel] SyncML topic revived (further down the rabbit hole)

2019-07-26 Thread Damien Caliste
Hello, Le 2019-07-23 13:41, deloptes a écrit : As my previous posts were not showing on the dev list, I write here to test if it works. In any case I'll be glad to receive some advises and review on the progress done. What I did is to - rebase btcalendar on current master and add late

Re: [SailfishDevel] SDK versioning

2019-07-26 Thread Slava Monich
Hi Rinigus, I would probably opt for some kind of a runtime version check, e.g. https://github.com/monich/sailfish-qrshare/blob/master/shareplugin/src/qrshareplugin.cpp I even use dlopen/dlsym hacks to work around Qt 5.2 -> 5.6 ABI breakage, which sounds slightly insane even to myself :) Nonet