Example client

[Adam Pigg]

So, i got something to work in a fashion.

According to my laptop, im paired with my phone.

To do this, i started a new project for a Sailfish app, and copied in core/
interfaces/ daemon/ and delcarativeplugin/

I commented out all the plugins, and removed bits depending on KF5
frameworks i havnt yet ported.  Fortunately, I had previously built a lot
of KF5 to aid in Kexi porting.  We dont have QWidget here, so anything
depending on that had to go, and there is no KNotification, so pairing
requests are blindly accepted atm!

The sailfish gui just has a list of local devices based on the DeviceModel,
but it auto starts the dbus daemon as it should.

So, progress...

On Sat, 10 Feb 2018 at 20:40 Nicolas Fella <feeenico at gmail.com> wrote:

> A1
> There isn't really a difference between Client and Server. The mobile and
> desktop backend should behave the same. The only major difference is that
> the Android one is written in Java and uses the Android libraries and the
> desktop one in C++/Qt. It's even possible to pair two desktops or two
> phones together. So I think there's a good chance that it even works out of
> the box.
>
> A2
> Since the current Bluetooth support is incomplete you should get the lan
> one running first. However, if you managed to fill the wholes in the
> Bluetooth one and get them both working that would be really really awesome.
>
>
> On Feb 10, 2018 21:26, "Adam Pigg" <adam at piggz.co.uk> wrote:
>
> Q1 :)
> Does core/backends contain an implementation of the mobile client side, or
> just the server side? (is there much difference?)
>
> Q2
> Should i focus on a lan connection or a BT connection?
>
> Ta
>
> On Sat, 10 Feb 2018 at 19:55 Adam Pigg <adam at piggz.co.uk> wrote:
>
>> Thanks for that, i'll take a look.
>>
>> Dont fear sailfish ... really, its just plain Qt/QtQuick 2 ... so, mostly
>> like a desktop, with some custom components for the look/feel, so,
>> hopefully wont take much bootstrapping.
>>
>> On Sat, 10 Feb 2018 at 19:01 Nicolas Fella <feeenico at gmail.com> wrote:
>>
>>> Hey guys,
>>>
>>> first of all I'm sorry, but I'm not familiar with Sailfish at all, but I
>>> really appreciate your interest in porting KDE Connect to it. In the
>>> core/backends folder of the kdeconnect-kde repo you find a implementation
>>> of the pairing in Qt/C++. Note that most plugins are pretty asymmetrical,
>>> e.g. for the MPRIS plugin the android repo acts as the controller and the
>>> one on the desktop as the controllee. Some plugins, like the ping plugin
>>> work the same in both directions. Take that into account when porting C++
>>> code from the desktop to a phone. In the app/ folder in the desktop repo
>>> you find a unfinished kirigami application that could serve as base for a
>>> Sailfish port. You need to add -DEXPERIMENTALAPP_ENABLED=on to the cmake
>>> command to build it.
>>>
>>> For any non-sailfish related questions feel free to contact me.
>>>
>>> Happy hacking
>>>
>>>
>>> Nicolas
>>>
>>> On Sunday, 11 February 2018 00:12:30 CET you wrote:
>>> > Hey piggz, I hope you remember me (adeen-s) from #sailfishos-porters
>>> > I have been working on Android and I'd love to help port kdeconnect to
>>> > sailfishos. I couldn't find anything related to it, but doesn't plasma
>>> > mobile have it? Maybe start looking there.
>>> >
>>> > On 10-Feb-2018 11:08 PM, "Nicholas Estrada" <116nic97 at gmail.com>
>>> wrote:
>>> >
>>> > > Haha gotcha. Totally misunderstood. Yeah all I did was write a simple
>>> > > frontend for the desktop commands. Nothing on the socket side or
>>> phone
>>> > > side.
>>> > >
>>> > >
>>> > > On Feb 10, 2018 at 9:07 AM, <Adam Pigg <adam at piggz.co.uk>> wrote:
>>> > >
>>> > > Is that a program that acts as if it were on a phone, talking to the
>>> > > kdeconnect desktop client? Or something to trigger the desktop app
>>> to send
>>> > > a command to the phone?
>>> > >
>>> > > Im after the first part ... something describing how to create
>>> either a BT
>>> > > or network connection to the desktop app, and how the protocol works.
>>> > >
>>> > > Cheers
>>> > >
>>> > >
>>> > > On Sat, 10 Feb 2018 at 15:21 Nicholas Estrada <116nic97 at gmail.com>
>>> wrote:
>>> > >
>>> > >> Hey, I wrote a pretty simple GUI just for SMS a bit ago. I was the
>>> one
>>> > >> who wrote it in Java, but then I ported it to C++/Qt.
>>> > >>
>>> > >> https://github.com/estradanic/ksms
>>> > >>
>>> > >> It does have a couple issues right now that I haven't gotten to
>>> fixing
>>> > >> because college kicked back in pretty hard. But if you want to take
>>> a look
>>> > >> at the code, be my guest. :)
>>> > >>
>>> > >>
>>> > >> On Feb 10, 2018 at 5:05 AM, <piggz1 <piggz1 at gmail.com>> wrote:
>>> > >>
>>> > >> Hi, is there any example client code written in qt/qml/c++, as
>>> opposed to android java?
>>> > >>
>>> > >> Im tempted to write a sfos client, and would appreciate some
>>> pointers in getting a client up and running with basic connectivity.
>>> > >>
>>> > >> Adam
>>> > >>
>>> > >> --
>>> > >> Sent from my Jolla
>>> > >>
>>> > >>
>>> >
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20180215/5cbe86c6/attachment-0001.html>