Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to open the menu widget from the terminal #11

Closed
ammen99 opened this issue Jan 24, 2019 · 5 comments · Fixed by #208
Closed

Add a way to open the menu widget from the terminal #11

ammen99 opened this issue Jan 24, 2019 · 5 comments · Fixed by #208

Comments

@ammen99
Copy link
Member

ammen99 commented Jan 24, 2019

This way we can bind such a command to a keybinding and open the menu with it.

@soreau
Copy link
Member

soreau commented Feb 15, 2019

dbus comes to mind, though I find the syntax unwelcoming (both the API code and dbus-send).

@AdrianVovk
Copy link

D-Bus is a fair choice for IPC. It's cross-platform (so the BSD port can use it), it's extremely cross-language, and it is stable. I can be a bit clunky in the c/c++ world, but it gets the job done, and works with many debug tools.

@soreau, if you don't like dbus-send, you can use busctl (if you use a systemd-based distro)

@ammen99
Copy link
Member Author

ammen99 commented Feb 15, 2019

What I find problematic is the case where we have multiple outputs (or even multiple Wayfire's running). How does the command know which instance to send it to? Perhaps we should just do a Wayfire plugin for tight integration with wf-shell.

@soreau
Copy link
Member

soreau commented Feb 15, 2019

@ammen99 With compiz there is a concept of screens for each call so the dbus-send caller would choose screen[n] for different instances or allscreens where it doesn't matter. (See the wiki for examples) For knowing which output, you could probably also build it into the call or just use the focused one.

@valpackett
Copy link
Contributor

valpackett commented Feb 15, 2019

In numbernine currently I have a launcher that just pops up as a layer-shell surface on an unspecified output when a gtk action is called, and a panel button that calls a gtk action over dbus. Absolutely no explicit mention of outputs anywhere, Wayfire just puts the lsh surface on the focused output, which is where the button was clicked :) So adding a keybinding is trivial.

multiple Wayfire's running

Each instance should have its own session bus.

clunky in the c/c++ world

gdbus-codegen-glibmm is awesome :) (but with gtk actions, you don't need anything like that)

soreau added a commit that referenced this issue Jan 14, 2024
Update wayfire-shell protocol and listen for the toggle_menu event.
Fixes #11 because ipc plugin can be used to allow calling toggle_menu
from a script.
soreau added a commit that referenced this issue Jan 15, 2024
Update wayfire-shell protocol and listen for the toggle_menu event.
Fixes #11 because ipc plugin can be used to allow calling toggle_menu
from a script.
ammen99 pushed a commit that referenced this issue Jan 18, 2024
* Listen for toggle_menu event

Update wayfire-shell protocol and listen for the toggle_menu event.
Fixes #11 because ipc plugin can be used to allow calling toggle_menu
from a script.

* wayfire-shell: Bump version for new toggle_menu event
ammen99 pushed a commit that referenced this issue Mar 13, 2024
* Listen for toggle_menu event

Update wayfire-shell protocol and listen for the toggle_menu event.
Fixes #11 because ipc plugin can be used to allow calling toggle_menu
from a script.

* wayfire-shell: Bump version for new toggle_menu event
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants