Re: [tuxdroid-user] Tuxdroid gamepad interface

[Philippe T. <ph...@te...>]

>> - light level
>> future: battery level
>>     
> Can be mapped to 2 analogs axis
>
>   
So the idea is to use an existing API but with such a mapping
you could hardly use it with anything else than the daemon.
Mapping the three buttons to joystick buttons allow basic control
of other softwares expecting a joypad but mapping light level
and battery level to analog axis make the tux hardly usable
as a joypad!
Shortly said: I don't see the benefit of mapping to an existing API
if the result could be used anyway only by the daemon
or tux-specific programs.
>> - IR codes
>>     
>
> Should use the GNU/Linux IR API (don't know it).
>   
I agree we could beneficiate from a separate API for the IR part.
I had a look to LIRC but it looks like there isn't much of common API here.
And we get directly RC5 codes while usually LIRC gets more raw data
and is therefore capable to understand a larger set of remote controls.
But we definitively need to find a way to hook the tuxdroid to lirc!
Note that looking to the firmware gives me the confidence the tuxdroid could
also receive more than just RC5 codes and the firmware could be as smart
as lirc to decode a variety of rc or pipe raw IR data to lirc.

> Well, I saw vlc for example, it let you specify you /dev joystick
> interface to use. But frankly, it's not tuxdroid problem and the user
> can simply unplug fux.
>   
If you plug sth pretending to be a joypad but acting as a mad joypad,
it's a tuxdroid problem :-)

Looks like I still need to be convinced ;-)

Maybe getting the 3 button events mapped to a USB mouse could help
(but no movements) so applications controlled by mouse buttons
(diaporama, ooimpress,...) can be controlled by the tux.

Phil