-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[feature request] Add Wayland support #159
Comments
What is necessary for native wayland support? Any pointers? I am a newbie in this field but maybe I can work on a PR... I am asking because I switched from i3 to sway a couple of days ago and wanted to use yad to build a small shutdown menu with the |
i don't use wayland. that's why i cannot add wayland support to yad |
Me too, but it would be nice if YAD worked without XWayland. There have been many cases recently (not mine). |
Yad seems to mostly work under Wayland, but a few features such as tabs (#109) and tray icons. So I think it's more a case of improving Wayland support. I'm not in any way familiar with the internal workings of Yad or Wayland implementations, but it seems like XDG Foreign Protol (which seems like an in-development spec?) should implement some of the functionality needed for tabs to work on Wayland. I guess for improved Wayland support it'll need to be contributed by someone else and it'll require waiting for the Wayland spec to implement features needed for Yad to have full Wayland support (i.e., alternatives to what is used on X11). Improved Native Wayland support would be excellent for Yad at some point in the future 🙏 |
adding
|
I have some ideas for how wayland support could be improved: notebook and panelsInstead of using xembed, have --plug serialize the options to a file, then have notebook and panel read those options and use them to create the sub-components. That could also allow creating a file beforehand. And/or have a way to specify the contents of each tab/panel on the same command line as the tabs itself. notificationI see two options here. The first is to change it to be a notification instead of a "status icon". Basically, use GNotification instead of Gtk.StatusIcon. I think this would be pretty straightforward to do, and would better fit the name. Unfortunately, it would fundamentally change how the feature works. The second is to use "more modern platform-specific APIs" outside of gtk, in particular the StatusNotifierItem protocol, probably with a library such as ayatana indicator library. The biggest problem with this, aside from probably adding a new dependency, is that AFAICT, there isn't any way to do it on vanilla gnome. There are extensions that provide support, but gnome itself refuses to implement SNI, from what I understand because of some limitations of the protocol, but they don't have any alternative. It's also basically linux specific, and I'm not sure if other platforms are supported by this project (although if it relys on xembed I'm guessing not). --mouseI don't think there is really anything that can be done about this unless a prototol is added to allow positioning toplevel surfaces somehow |
Add Wayland support (without Xwayland).
And thinner widgets in height like 9.3 version (9.3 is latest with "normal" height ).
The text was updated successfully, but these errors were encountered: