kde connect gamepad plugin

[Albert Vaca]

I would like to know if it's possible to register an application as a
"virtual controller" in Xorg. That would be more like the video that you
shared than just sending keyboard input. On a phone screen you can simulate
a joystick, but if it's implemented like a keyboard it will only work like
a 4-direction game pad. If we can emulate a controller, we will be able to
simulate an actual joystick. Also, lots of games are already programmed to
support XBox controllers, so they would work without any extra
configuration. Have you investigated this possibility?

On Sun, Mar 29, 2015 at 4:15 PM, Aleix Pol <aleixpol at kde.org> wrote:

> On Sun, Mar 29, 2015 at 1:28 PM, Konstantinos Athanasiou
> <dinosath0 at gmail.com> wrote:
> > hello i am new here and first time contributing in a open source
> project. I
> > would like to work on the gamepad plugin that was proposed and would
> like to
> > hear your opinion.
> I love the idea. :)
>
> >
> >
> > * My idea was to have 2 buttons when you open the plugin. One button for
> the
> > gamepad and one for the editor. When you open the gamepad a list of
> > layouts/themes is shown (e.g. psx,ps2,xbox etc) and you chose your layout
> > and start playing. In the editor you can edit a layout/theme. You can
> edit
> > the button icons, add actions (e.g. in openmorrowind open chest, start
> > playing playlist from library etc) and assign hardware keys to button
> (for
> > tablets with gaming buttons).
> Implementing editors on end-user applications hasn't been ideal in
> some projects I've worked on. Maybe you'd like to start by
> implementing some simple format that can be sent from the game host?
>
> >
> >
> > * Now about implementation what do you think? Sould i send a message to
> the
> > server when a key was pressed or should i send a message with the gamepad
> > state in very short intervals( eg button1:pressed ||
> button2:not-pressed) or
> > keep both and change in settings?
> Well, logic suggests that the less you send, the better. KDE Connect
> protocol is admittedly quite verbose. I think that the biggest
> decision you'll have to take is whether you want a persistent transfer
> (i.e. a socket) or to send a package every time a key is pressed. How
> you send it will depend on the approach you choose.
>
> >
> >
> > * Lastly some more ideas i had about the actions for the buttons. For
> media
> > controls we already have the mpris plugin , we also have have the
> keyboard
> > plugin and touchpad plugin and hopefully many more coming.
> >
> > But what if wanted to have all those plugin in one screen? How about all
> > these separate plugins were all simply buttons you can edit in the
> editor?
> > What do you think?
> I'm not sure I understand what you mean. If what you mean is that you
> want to send mprisplugin packages from your interface, then it's
> technically possible but maybe it will overcomplicate it. I'm unsure.
> I'd suggest to start by implementing the joystick API's and iterate
> from there.
>
> >
> >
> > I was inspired by GestureWorks Gameplay app. You can check it out here:
> >
> > https://www.youtube.com/watch?v=0jfBqIheW-w
> >
> >
> > Also , can you please tell me how to build kdeconnect in kubuntu 15.04 ?
> If
> > it is hard i can do it in kubuntu 14.04.
>
> I'd recommend 15.04, we're requiring some recent features in KF5, so
> it will be easier for you.
>
> Cheers!
> Aleix
> _______________________________________________
> KDEConnect mailing list
> KDEConnect at kde.org
> https://mail.kde.org/mailman/listinfo/kdeconnect
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20150330/c3ad41d0/attachment-0001.html>