Thanks for your fast replies! I think I really need to dig into that a bit more. I am actually working (as I just started) with clutter-1.2.12 on a "normal" nvidia linux machine and was suprised of the easyness! Even bringing together beagleboard (OMAP3530) and clutter does not look to difficult, so I am actually testing different setups (with/without X-Server).
Are you guys having a hint, what would be the best combination to create a nice clutter/omap gui, maybe with gstreamer (as I worked with that before) as there are decoder libraries from TI avialable. Thanks again ps: for those who like visual effects ;-) http://vimeo.com/14413275 ----- Ursprüngliche Nachricht ----- Von: Damien Lespiau Gesendet: 17.09.10 13:11 Uhr An: [email protected] Betreff: Re: key events on framebuffer On Fri, 2010-09-17 at 10:07 +0100, [email protected] wrote: > Hi everybody, Hi, > today I was able to compile clutter for the OMAP3530 and my simple > apps work quite ok, so many thanks for the work on that! > > Now I come to the point where I would like to add user interaction via > keyboard or mouse. The (maybe stupid) question is, if I don't have an > x-server to handle all my events, how can I receive them with clutter? If you have the usual input event drivers /dev/input/eventX, you can open the device and wait for events from there. This happens when plugging a USB keyboard or mouse or possibly a simple "2/3 keys keyboard" connected with a few GPIOs to the CPU. The best way to integrate this with Clutter's GMainLoop is to use a GIOChannel to wait and read from the file descriptor and create events from that. The structure you read from input devices, struct input_event is defined in <linux/input.h>. Now, you can make a number of refinements to the basic principle. Add a key board layout layer, try to look at X to reuse some stuff, add integration with udev (gudev) for the discovery of devices and hotplug, etc... keylib (http://sourceforge.net/projects/keylib/), mentioned in an other answer seems to read from the virtual terminal instead of the input devices directly and provides some integration with X (xmodmap files). It does the job but I think it would be better for clutter to have direct access to the list of devices you have on your system and handle things from there. Googling around, you can find quite a bit of resources about input devices, say http://www.linuxjournal.com/article/6429 HTH, -- Damien
_______________________________________________ clutter-app-devel-list mailing list [email protected] http://lists.clutter-project.org/listinfo/clutter-app-devel-list
