General info on creating a window in Wayland
Hi all, I'm using Arch linux 32 bit to develop a sample application on Wayland. My question is, if I've installed the Wayland and Weston packages using pacman, shouldn't the files (headers and libraries) used to run the client examples in the Weston source exist after installation of these pacakges? If not, are there any example clients that DO use the files installed by the Wayland and Weston packages? My point is, I expect to be able to develop code using system headers and libraries installed by the packages, and I'd rather not download and build the source every time an update becomes available. I'd rather use 'pacman -Syu' to do the updates. An example would be the weston/clients/window.h or weston/shared/os-compatibility.h. I'd at least expect there to be a version of window.h in the system headers coming from the Arch package. Is this an issue with the Arch linux package creators? I'm new to Wayland, and all I'm trying to do is show a window on the Wayland display. Most of the examples I've looked at don't seem to refer much to the system headers and libraries, apart from the most common ones installed by the packages. If anyone can give me some guidance, I'd appreciate it. Thanks Mike ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: libinput: Support for long press key detection?
Am 21.10.2014 um 21:03 schrieb Carsten Haitzler (The Rasterman): On Tue, 21 Oct 2014 20:21:26 +0200 Stefanie Behme steffi.be...@gmail.com said: Hi, on last ELCE in Duesseldorf I learned that the development of libinput was started to handle input devices in Wayland compositors. I had a look in the API documentation and found that the enum libinput_key_state has these values: LIBINPUT_KEY_STATE_RELEASED and LIBINPUT_KEY_STATE_PRESSED. There is a need to detect if a key is pressed (and hold) for a certain amount of time. If this is the case a long-press key event is send. It is also possible that several long-press key events are defined for one key, e.g.: - 500 ms: KEY_STATE_LONG_PRESSED_1 - 1000 ms: KEY_STATE_LONG_PRESSED_2 - 5000 ms: KEY_STATE_LONG_PRESSED_3 A long press on a key is e.g. used to create a screen shot. Is there any plan to support this kind of long press detection? How could this look like? Any ideas? can you explain why this needs or should be done at the libinput level and not in the app/toolkit where it already is handled (at least in some toolkits). Since the input handling code was put in an own library to avoid duplicated code I was wondering if long press detection could also be part of libinput. Then this has not to be implemented in every app/toolkit. Regarding the answer from Peter, that this would be too high level for libinput, just for my information I wonder where is the border of libinput? Which kind of input handling will be part and which not? Best regards Steffi ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: libinput: Support for long press key detection?
On Sun, 26 Oct 2014 13:10:43 +0100 Stefanie Behme steffi.be...@gmail.com said: Am 21.10.2014 um 21:03 schrieb Carsten Haitzler (The Rasterman): On Tue, 21 Oct 2014 20:21:26 +0200 Stefanie Behme steffi.be...@gmail.com said: Hi, on last ELCE in Duesseldorf I learned that the development of libinput was started to handle input devices in Wayland compositors. I had a look in the API documentation and found that the enum libinput_key_state has these values: LIBINPUT_KEY_STATE_RELEASED and LIBINPUT_KEY_STATE_PRESSED. There is a need to detect if a key is pressed (and hold) for a certain amount of time. If this is the case a long-press key event is send. It is also possible that several long-press key events are defined for one key, e.g.: - 500 ms: KEY_STATE_LONG_PRESSED_1 - 1000 ms: KEY_STATE_LONG_PRESSED_2 - 5000 ms: KEY_STATE_LONG_PRESSED_3 A long press on a key is e.g. used to create a screen shot. Is there any plan to support this kind of long press detection? How could this look like? Any ideas? can you explain why this needs or should be done at the libinput level and not in the app/toolkit where it already is handled (at least in some toolkits). Since the input handling code was put in an own library to avoid duplicated code I was wondering if long press detection could also be part of libinput. Then this has not to be implemented in every app/toolkit. Regarding the answer from Peter, that this would be too high level for libinput, just for my information I wonder where is the border of libinput? Which kind of input handling will be part and which not? to implement longpress you need to implement timeouts - this is where it begins getting high level and far more hairy than libinput is. toolkits already do this and have timeout infra with their mainloop handling. they also do press vs drag handling too with hysteresis. should libinput do this too? then where is the drag point? n pixels from first touch? at boundary of widget? if there is a boundary - where is it? often dragging out of the widget cancels the click action - again widget sets do this. should libinput do it? you are looking at a long and obstacle-filled slippery slope to put this kind of thing in libinput. - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: General info on creating a window in Wayland
2014-10-26 10:45 GMT+02:00 Michael Johnson mikeyj...@hotmail.com: Hi all, I'm using Arch linux 32 bit to develop a sample application on Wayland. My question is, if I've installed the Wayland and Weston packages using pacman, shouldn't the files (headers and libraries) used to run the client examples in the Weston source exist after installation of these pacakges? If not, are there any example clients that DO use the files installed by the Wayland and Weston packages? My point is, I expect to be able to develop code using system headers and libraries installed by the packages, and I'd rather not download and build the source every time an update becomes available. I'd rather use 'pacman -Syu' to do the updates. An example would be the weston/clients/window.h or weston/shared/os-compatibility.h. I'd at least expect there to be a version of window.h in the system headers coming from the Arch package. Is this an issue with the Arch linux package creators? No. window.h is part of toytoolkit, which is a toy and is not meant to be used outside of weston's example clients. Weston does provide a few headers to be used by other projects but they are for developing weston plugins, not for developing wayland clients. If you just want to write a wayland client all you need are wayland headers and the xml files of any additional protocols you may choose to use. clients/simple-shm.c in weston is a very simple example client which doesn't use toytoolkit, so you may start by looking at its code. -- Giulio I'm new to Wayland, and all I'm trying to do is show a window on the Wayland display. Most of the examples I've looked at don't seem to refer much to the system headers and libraries, apart from the most common ones installed by the packages. If anyone can give me some guidance, I'd appreciate it. Thanks Mike ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
