-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
UI / Performance: Remove dependencies on AWT (system tray icon) #4940
Comments
Looks like we also use AWT for the webcam/QR code reader, via the class As per https://stackoverflow.com/questions/30970005/bufferedimage-to-javafx-image there is a JavaFX equivalent to that. |
Besides that it also stopped working with Catalina as it doesn't work without notarization anymore to access the webcam. So I think it would be good to tackle the webcam part anyways. |
Related to #4374. |
There remains outstanding issue of the library |
And we really need to get rid of it now:
It prevents us to build notarized versions now for macOS as well. |
I'll give JavaCV a shot if I'm able to port our QR-Code reader to this supported lib. |
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 closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
This restores the functionality that was removed in b5beea5. However, this implementation utilizes the JavaCV library rather than the webcam-capture library as discussed in bisq-network#4940. As a result, this should now provide macOS support.
This restores the functionality that was removed in b5beea5. However, this implementation utilizes the JavaCV library rather than the webcam-capture library as discussed in bisq-network#4940. As a result, this should now provide macOS support.
As per https://stackoverflow.com/a/11121207 having AWT dependencies in a JavaFX application can lead to more CPU/RAM usage than necessary, because two separate graphics stacks are loaded and active at the same time.
From what I can tell, Bisq mainly uses AWT for the system tray icon.
If that's the case, then with AWT we have:
To me, it seems the drawbacks outweigh the benefits.
Therefore, I suggest to remove the AWT dependencies from Bisq (and with that, the system tray icon).
The text was updated successfully, but these errors were encountered: