Re: JOGL 2.0 (OpenGL/OpenGL-ES) backend for LibGDX
Posted by Sven Gothel on Jan 17, 2013; 3:11am
URL: https://forum.jogamp.org/JOGL-2-0-OpenGL-OpenGL-ES-backend-for-LibGDX-tp4027689p4027881.html
On 01/17/2013 04:01 AM, Xerxes Rånby [via jogamp] wrote:
> noxo wrote
> Would be nice to start work on that console based input listener...
>
> I have started some work on a NEWT LinuxEventDeviceTracker, the keyboard
> parser is about done but it needs testing.
> https://gist.github.com/ec17597f5c079708ce72
>
> java -cp jogl/build/jar/jogl-all.jar:gluegen/build/gluegen-rt.jar
> jogamp.newt.driver.linux.LinuxEventDeviceTracker
>
> This tracker is intended to parse all of the Linux /dev/input/event* files but
> in the version posted here it currently only track one hardcoded file name.
>
> The event dev files are nice they contain events from all keyboard, mouse
> wheel, mouse, joystick, audio jack connections, power buttons etc connected to
> a linux system, all using the same.. easy to parse event interface!
> http://www.kernel.org/doc/Documentation/input/input.txtGreat stuff!
Regarding daemon thread lifecycle:
- start @ 1st device nativeOpen
- stop @ last device nativeClose
.. hence we need a NEWT device association, i.e. impl.,
but I guess we already have that due to RaspPi.
Yeah, and then the looong discussion about virtual keycodes,
i.e. independent of current keymap - see Bug 641
<https://jogamp.org/bugzilla/show_bug.cgi?id=641>
~Sven
URL: https://forum.jogamp.org/JOGL-2-0-OpenGL-OpenGL-ES-backend-for-LibGDX-tp4027689p4027881.html
On 01/17/2013 04:01 AM, Xerxes Rånby [via jogamp] wrote:
> noxo wrote
> Would be nice to start work on that console based input listener...
>
> I have started some work on a NEWT LinuxEventDeviceTracker, the keyboard
> parser is about done but it needs testing.
> https://gist.github.com/ec17597f5c079708ce72
>
> java -cp jogl/build/jar/jogl-all.jar:gluegen/build/gluegen-rt.jar
> jogamp.newt.driver.linux.LinuxEventDeviceTracker
>
> This tracker is intended to parse all of the Linux /dev/input/event* files but
> in the version posted here it currently only track one hardcoded file name.
>
> The event dev files are nice they contain events from all keyboard, mouse
> wheel, mouse, joystick, audio jack connections, power buttons etc connected to
> a linux system, all using the same.. easy to parse event interface!
> http://www.kernel.org/doc/Documentation/input/input.txt
Regarding daemon thread lifecycle:
- start @ 1st device nativeOpen
- stop @ last device nativeClose
.. hence we need a NEWT device association, i.e. impl.,
but I guess we already have that due to RaspPi.
Yeah, and then the looong discussion about virtual keycodes,
i.e. independent of current keymap - see Bug 641
<https://jogamp.org/bugzilla/show_bug.cgi?id=641>
~Sven
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |