-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Implement a new Bluetooth indicator #459
Conversation
bd40752
to
52e379e
Compare
FYI - Debian has now marked the usage of libgnome-bluetooth13 as something to be removed before its next release since upstream has dropped support. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030130 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059486 So great news that we have this PR - nice one @EbonJaeger This also dropping support from BCC as well - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059485 ... but with the need to pair devices via BCC that's more problematic - we would have to rewrite this whole section in BCC ... either with the suggested new gnome library ... or a complete rewrite to use bluez? EDIT: or maybe less elegant but very little work - just drop bluetooth from BCC entirely - and add here a callout to blueman to-do the GUI pairing aspects? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Been using Bluetooth applet and it connects / disconnects just fine with my Fairbuds XL headphones. Battery constantly reports 100% but I'm leaning on that being more an issue with upower than anything else. I'll re-install d-spy and take a look.
Some feedback provided mainly on sendto, some interesting logic for formatting time and duplication that should ideally be avoided.
Design feedback: Maybe could do with some padding around the edges of the popover contents. Night Light and Sound Indicator are a couple examples, but the padding may only really be visible (excluding Night Light header where it's hardcoded into the widget code) when using Materia. Not sure about other themes when they are used in conjunction with the internal theme.
Overall, fantastic work. I can see a lot of care and attention went into this.
52e379e
to
fc3e00d
Compare
Rebased it, ignore noise on the billion commits after my suggestions :D |
I was wondering why some of the review items were showing "outdated" xD |
The latest commit addresses the duplicated code and estimated time calculation. If you could test receiving a file via Bluetooth, that would be great. I'm not getting the notification to reject or accept the transfer, and I have no idea if it's the code, my phone, or the deity of Bluetooth deciding to mess with me. |
@EbonJaeger I am able to send files from my desktop to the test phone just fine but sending from my test phone to the desktop, getting the notification to accept and accepting it, does not work. Just to be sure, I tested it with a unique file not on my desktop. Also as a note, we need a newline between the From: FILEPATH and "Sent to: DEVICE". Otherwise it all melds into one line. Will continue testing but hopefully @fossfreedom can do some further testing on his end too since he uses sendto functionality (or at the very least I know he certainly does with more frequency than me -- which is never :D) Otherwise, LGTM. Send-to dialog looked good, though we may want to consider filtering out devices you really can't send to like headphones and wireless keyboards. |
|
hmm - I'm wonder if the send and disconnect buttons should be added to a buttonbox rather than pack-start within a box? If I connect to a phone via the popover the disconnect button appears in the popover. Good. However the send button doesn't appear. If I restart the panel then both the send button and disconnect buttons appear in the popover. |
@fossfreedom I think I might have it this time. Can you try the latest commit? |
Nice work! Relief issues have been resolved. Connected my phone - send files button enabled. Connected my airpods - connected - no send files button - so thats good news. |
good to be merged IMHO. |
(I hope... The organization is a mess.) Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
At this time, I have no idea how to integrate the UPower aspect with the Bluetooth devices. Moreover, I can't test if it's working even if I did, because none of my Bluetooth devices trigger the UPower signals. Signed-off-by: Evan Maddock <[email protected]>
It'll automagically figure it out for DBus. Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Also fixes saving received files to the Downloads folder. Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
This means that the sending device will no longer still send the file, even if the transfer was rejected. Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Co-authored-by: Joshua Strobl <[email protected]>
Both the send and receive dialogs are almost the same, the main difference being in the background implementation and wording of strings. This causes some duplicated logic, especially around the formatting of times remaining. This adds a new base class that both dialogs can derive from while still having their own implementations for doing the work, leading to less duplicated code. Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
Signed-off-by: Evan Maddock <[email protected]>
76ea84e
to
891839e
Compare
Description
The Bluetooth rewrite is finally here! GNOME Bluetooth is entirely dropped from Budgie Desktop; we now use Bluez and UPower directly, giving us full control over how Bluetooth is interacted with. You will now be able to connect to and disconnect from your Bluetooth devices from the panel without having to go to the Control Center. You will still have to visit the Control Center to pair new devices, however. With the direct usage of UPower, you will also see the battery power of devices that report it right in the applet popover.
This also includes our own implementation of Sendto in order to send and receive files over Bluetooth. Budgie Sendto is very heavily inspired by Elementary's own Bluetooth Sendto implementation. It runs in the background to listen for file transfer requests from other devices, showing a notification when one is received, enabling you to accept or reject the transfer. To send a file, you can open the Bluetooth indicator popover and hit the Send button to open a dialog to choose what device you want to send to.
Closes #197
Submitter Checklist
git rebase -i
(if needed)