On 25 October 2017 at 09:40, Listings - www.majors-welt.net <list...@majors-welt.net> wrote: > Hi folks, > > i write here, because i dont know where it may fit.
You probably want to start a discussion on wayland-devel: https://lists.freedesktop.org/mailman/listinfo/wayland-devel This list is for developing GTK applications. > I am a user of a color-picker tool - previously Gcolor2 - that has now been > adopted to Gnome3 -> Gcolor3 -> https://github.com/Hjdskes/gcolor3/ > > Now while lots of linux distributions are switching to wayland as default > session the color picking just dont work any more (which breaks the workflow > of web and other developers) - even not in gimp afaik. Correct; the idea is that only privileged components can access the contents of the screen, and that applications need an appropriate privilege escalation mechanism, usually by talking to those components through a well-defined IPC mechanism, like DBus or a Wayland protocol extension. Starting from a sandboxed environment and opening it up appropriately is safer and more secure than having an open system and closing it down. > The developer of Gcolor3 has no straight idea how to fix this (and maybe > some "wayland-api" is neccessary?) You probably want to start with a compositor-specific API, like the way screenshot and screen recording is performed in GNOME; if you want more Wayland compositors to follow the same protocol, you will have to draft the specification and discuss it on wayland-devel in order to get buy in from all the developers of Wayland compositors out there. Ciao, Emmanuele. -- https://www.bassi.io [@] ebassi [@gmail.com] _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
