Re: [i3] [i3lock] blur effect
Hello, Now I have had time to test and develop more. Initial bugs are fixed. The repo address is https://github.com/karulont/i3lock-blur/ I also made a release https://github.com/karulont/i3lock-blur/releases/tag/2.5.1 For archlinux users as myself I also made an AUR package called i3lock-blur. Now i3lock-blur is easier for you to test and see if you like it. -- Best wishes, Karl
[i3] [i3lock] blur effect
Hello, I am a new i3 user and I used a wrapper for i3lock. https://github.com/ashinkarov/i3-extras/blob/master/i3lock-wrapper This wrapper script takes a screenshot of the desktop before starting i3lock. Then it blurs it and uses that blurred screenshot as the background for i3lock. I was a little bored and little unsatisfied with the script. So I wanted to make it better. As a result of learning and hacking, I can now present to you a i3lock fork. https://github.com/karulont/i3lock-blur/tree/fuzzy It uses COMPOSITE extension to get the windows current state. It uses DAMAGE extension to know when to redraw. It uses OpenGL to blur the image. Currently there is a lack of error checking, but I am still working on it. But interested parties can get the fuzzy branch, build it using make. And test the new blurred background feature by using cmdline switch '-f' (f for fuzzy). Example: cd directory make ./i3lock -f -- Best wishes, Karl
Re: [i3] [i3lock] blur effect
Hi Karl, nice idea, but I don't really understand why you not just draw on i3lock's window? That way you don't have to maintain a fork, we keep the number of forks to a minimum (so… 0 hopefully ^^) and still everyone gets to implement their favourite thingy as a wrapper. You can use xwininfo -name i3lock or something similar to get the window id of i3lock. Just a thought. Best, Axel
Re: [i3] [i3lock] blur effect
On 03/04/2014 09:34 PM, Axel Wagner wrote: nice idea, but I don't really understand why you not just draw on i3lock's window? That way you don't have to maintain a fork, we keep the number of forks to a minimum (so… 0 hopefully ^^) and still everyone gets to implement their favourite thingy as a wrapper. You can use xwininfo -name i3lock or something similar to get the window id of i3lock. At first I didn't even knew what I was doing. Now I could write my own program, which paints on the i3lock's window. But then there would be a race condition between i3lock drawing and my wrapper drawing. And I wouldn't get a good result. I understand that forks are kind of unwanted. I created this just out of boredom. If the guys here think that this feature might be added upstream, I would be very happy about it. But currently this is not yet ready to be used by the masses. Best regards, Karl
