Translation of click events to touch events in kwin.

[Bhavisha Dhruve]

On Wed, Jun 8, 2016 at 7:37 PM, Martin Graesslin <mgraesslin at kde.org> wrote:

> I just discussed a little bit with Bhushan about how the emulator should
> work.
> I think it doesn't make sense to have kwin_wayland as the "toplevel"
> window,
> we rather need to make KWin a child of the emulator window to have things
> like
> useful controls around the window. Think of e.g. the control in VirtualBox.
> That was kind of what I had in mind when I suggested to use the fake input
> protocol. The emulator window can listen for mouse events and then send
> them
> as touch events to the fake input protocol.
>

Prior your email, the thing which I understood was that windowed
kwin_wayland will be passing touch events. Thank you for clearing up my
this confusion.

>
> Now on how to embed KWin into another application. It's not as difficult
> as it
> sounds and I had a neat idea in my head for some time: a declarative plugin
> which would allow embedding KWin. This could then look something like:
> KWin {
>     id: kwin
>     socketName: "kwin-emulator-wayland-0"
>     anchors.fill: parent
>     Component.onCompleted: kwin.start()
> }
>
> Technically the QtQuickItem needs to forward input events (which could
> just be
> done through fake input) and render what the nested KWin provides. I see
> two
> possible solutions for that:
> 1. another Wayland compositor
> 2. base it on https://phabricator.kde.org/D1231
>

I now properly understood the actual idea, and how I will have to use
FakeInput interface, to sum up there will be QtQuick component, which will
be used by Plasma mobile emulator to embed KWin inside emulator window.

>
> Option 1 might be easier right now as we already have everything for that
> in
> place.
>

I really have no idea on which of the two solution you proposed will be
good choice, so can you please explain one which you think will be best in
details?

>
> If the whole thing sounds somewhat sane to you I can explain in more detail
> how that could work.
>

Thanking you in advance.

Awaiting for your earliest reply.

With Regards,
Bhavisha Dhruve.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160608/f8999b07/attachment.html>