Replies: 1 comment 1 reply
-
Thanks for putting the time into this, they're great suggestions. For a lot of them I'm at the mercy of Tauri's systray icon implementation which is a bit limited/difficult. I'm going to put together a feature pipeline so will add these under the UI section. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thank you for your efforts and your work.
Here are a couple of ideas that could greatly improve the interface usability :
Single instance ! If TunnlTo is currently connected to a tunnel, if we open a second instance and terminate it, the tunnel from the first instance is also closed ! This should never happen. See next point for visual feedback.
Icon should reflect the connection status, for example : green connected / red disconnected. May be also implement a watchdog to insure the connection is kept alive (see point above)
Hoovering over the icon should indicate, in a tooltip, to which server we are currently connected (that's the all idea of having profiles), without reopening the main window
Right click on icon show quick menu to Disconnect/Reconnect to the latest server... or display the list of available servers to chose from
Toggle main window display/icon with single left click on the icon
Sort list of saved tunnel configurations to select from
When adding a new tunnel, if importing, use the file name as default tunnel name
Resizable at least / Smaller main window (use screen density) ; remember size and position
Light / Dark theme (I believe it's in the pipeline)
Make a free entry textbox in the application settings (not tunnel settings), to be able to pass optional parameters to the wiresock-client program (log, lac...) ; I think you add per default -log-level debug, we should be able to configure this optionally
Option box to show or hide the console, in order to monitor traces
Portable version ?
Beta Was this translation helpful? Give feedback.
All reactions