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 options to MacOS menu bar menus #74

Open
nicknlsn opened this issue Sep 9, 2023 · 7 comments
Open

Add options to MacOS menu bar menus #74

nicknlsn opened this issue Sep 9, 2023 · 7 comments
Labels
wishlist Low priority nice to have features

Comments

@nicknlsn
Copy link

nicknlsn commented Sep 9, 2023

Feature request: it would be nice to have things like server settings and layout accessible from menu options.

@qu1ck
Copy link
Member

qu1ck commented Sep 9, 2023

You probably mean the system menubar that only mac has.
I agree that it would be nice but it's a very small benefit for a disproportionate amount of work, I'll leave this as a wishlist item.

In case anyone wants to implement this you would need to add menu items in macos.rs, add handlers for them in main.rs that would send a custom event to frontend, add handlers in frontend that would trigger corresponding actions.

@qu1ck qu1ck added the wishlist Low priority nice to have features label Sep 9, 2023
@qu1ck qu1ck changed the title Add options to menu bar menus Add options to MacOS menu bar menus Sep 9, 2023
@dukobpa3
Copy link
Contributor

dukobpa3 commented Jan 7, 2024

I can try to do it but let's discuss list of options in this menu, their grouping etc...

@qu1ck
Copy link
Member

qu1ck commented Jan 11, 2024

This is what end goal looks like for me, not everything has to be implemented at once:

TrguiNG menu

Create torrent...
Toggle theme
Toggle font size ?
Change layout
---------
Server settings
Application settings
---------
About
Close window
Quit

Torrents menu

Basically same as context menu
image

Window menu

list of current open tabs
---------
Connect submenu -> list of unopened configured servers
---------
current items (minimize, zoom, close)

It's been a while since I used MacOS so if the above is breaking any conventions it can be rearranged but from I recall there were plenty of apps that basically did whatever they wanted in menus.

Note that a lot of menu items would only work when the window is open even though the menu is still there when it isn't. So they would probably need to be disabled/hidden when window is not open. Keeping frontend and backend synchronized, updating menus and patching through the event calls will not be just a couple lines of code.

@Algwyn
Copy link

Algwyn commented Jan 20, 2024

Native system menu bar items would be nice, but indeed not critical ...
In term of menu structure, I would suggest the following:

trguiNG menu

Limit to app level actions. It would match the actions linked to these icons:
image

  • About
    ---------
  • Settings
    ---------
  • Toggle theme
  • Toggle font size
    ---------
  • Hide TrguiNG
  • Quit

Servers menu

  • Connect submenu -> list of unopened configured servers
  • Server settings -> settings of active tab server
  • Turn alternative bandwidth mode
  • Disconnect -> list of connected servers (or simpler, disconnect current tab)
  • Add server

Torrents menu

Options in context menu would be great, but maybe too detailed. The top left icons actions would probably be enough and simpler to implement:
image

  • Add torrent file
  • Add magnet link
  • ---------
  • Other actions from context menu
  • Start torrent
  • Pause torrent
  • Remove torrent
  • Queue sub-menu (Move to top, up, down, bottom)
  • Move torrent
  • Tags
  • Priority sub-menu

View menu

Actions from the Toggle button

  • Change layout
  • Toggle filters
  • Toggle details

@Metal-Snake
Copy link

I want to do the necessary changes to the menu. Personally I was annoyed by the missing Hide command. Adding that was easy, works just fine. But for a PR I would do the full menu. But I don't understand how to add a command like "Add Torrent".

In macos.rs I added a menu entry with the ID "addTorrent", now what do I need to do in main.rs? I think I need the serverModal somehow, but no idea how to get it.

.on_menu_event(|event| {    
            match event.menu_item_id() {
                "addTorrent" => {
                    // get the serverModal somehow and call AddTorrent?
                }
            }
        });

@qu1ck
Copy link
Member

qu1ck commented Nov 17, 2024

There is ongoing effort to migrate TrguiNG to tauri v2 which will affect the code you are touching, you might want to do your changes on top of tauriv2 branch. Btw if you are a macos dev then fixing or at least root causing the crashes of tauri v2 version on mac will have more impact.

On the topic: the way you communicate with frontend is through events. You can't get specific modal from rust because "modal"s which are just html elements only exist in the frontend. The algo on backend should be like this:

  1. Check if the main window is visible
  2. If not visible, then show, wait for frontend to load (it sends listener-start event) and then
  3. Send show-modal event with modal id as data

On frontend you add a listener to show-modal event to pop the corresponding modal in javascript. You can add the listener in Server component, just make sure to do it only in TAURI context (web app version of TrguiNG shares the same frontend code but obviously will not have any backend event system)
Example

@Metal-Snake
Copy link

I'm not really familiar with tauri and rust (yet?), but I will give it a try to check the tauri v2 branch.

For now I finally got the Open Torrent menu to work. Before I do the rest of the menu it would be great if you could have a look at what I did so far.
I committed it here: Metal-Snake@15ea365

macos.rs:
I replaced the CustomMenuItem "Quit" with a native one. Is that ok, or was there a reason to have it custom?
Is there a reason why the app_name and "View" menus are created inline, using the fluent interface, while the others don't? Is one way favored over the other?

main.rs and servermodals.tsx:
Is the code in the right place, coded the right way?

hotkeys.ts:
The cmd+h hotkey to setPriorityHigh conflicts with the Hide command, so I changed that to ctrl+h for now. Weirdly, before my change, cmd+h and ctrl+h both triggered the setPriorityHigh event. Same for setPriorityNormal, setPriorityLow and focusSearch. But selectAll doesn't work at all cmd+a does nothing while ctrl+a moves the cursor to the front which is the emacs shortcut which are also built in into macOS .
But maybe we can just not run that code block on mac when all those commands are added to the menu.

toolbar.tsx:
Oh no more hotkeys. The cmd+o hotkey to toggleFiltersPanel conflicts with the new "Add Torrent" menu. I used cmd+o for that as it's the default for open file actions. I think it makes sense to change those hotkeys on other systems to, as ctrl+o is used for open basically anywhere. I'm in favor of using 1, 2, 3, 4 for those toggles. That would also be more compatible with non english keyboards. Like the "[" character is typed using alt+5 (mac) or alt+8 (windows) on German keyboards. So it just won't work as it is.

So, what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wishlist Low priority nice to have features
Projects
None yet
Development

No branches or pull requests

5 participants