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
Spike around notification library beeep #3165
Comments
While we can make a toast appear with this library, we need to make sure in
this spike that the an error is shown when an error occurs (and possibly
link to a file that contains the full log).
So perhaps you need to split the work into two parts: 1. make sure we can
have a toast appear on all platforms (when possible), 2. show error in a
concise and detailed format.
|
gen2brain/beeep#18 seems it is not possible to open a related application yet? |
So the library will work for us in case of windows, but for that we can directly use the https://github.com/go-toast/toast. In case of macOS it cannot show an application icon on the notification (unless we make the binary an app bundle) also, upon clicking on the notification it opens up a File Pick windows (finder like) which seems to be the default and cannot be changed. @gbraad Yes, in macOS it does not support opening a related application, by default it opens that file picker window i mentioned. |
I think we can conclude the spike. It feels like this library will not help us much... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is for a spike around the library https://github.com/gen2brain/beeep for implementing notifications in systemtray. There's also another library for dialogs and popups which might be worth looking at https://github.com/gen2brain/dlgs
Ref: #3154
The text was updated successfully, but these errors were encountered: