Opened 19 months ago

Last modified 19 months ago

#17076 new task

[Deskbar Applets] Integrate USBDeskbar Deskbar Applet Into Codebase

Reported by: CodeforEvolution Owned by: nobody
Priority: low Milestone: Unscheduled
Component: Applications Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

In an age where essentially all external peripherals are connected through USB, I think that including USBDeskbar in the Haiku release image would be very handy for a user dealing with lots of connected devices (especially since the Devices preflet currently does not enumerate connected USB devices). Not to mention, USBDeskbar already handles USB connect and disconnect sounds which is currently not implemented within Haiku itself (ticket #16674).

USBDeskbar is currently available to install from HaikuPorts on both x86_gcc2 and x86_64 architectures.

Additionally, the code for USBDeskbar is currently available here at HaikuArchives: https://github.com/HaikuArchives/USBDeskbar

Notable problems:

  • The code is currently under a GNU GPL V1 license
  • Device info display is partially broken
  • The code needs to be cleaned up for Haiku styling

Change History (4)

comment:1 by pulkomandy, 19 months ago

I don't think we want it in Haiku? Why not simply package it at haikuports and install it if you like it?

USB connect/disconnect sounds I think are just annoying and useless. When you connect a device, it should just immediately work. The only OS which makes a big event about it by playing sounds, showing a window to install drivers, etc, is Windows.

Why do you need to waste DeskBar space just to see your USB devices? Why not just make sure the devices show in the Devices preferences if you ever need to list them?

comment:2 by CodeforEvolution, 19 months ago

I understand your concerns, however, here’s more detailed reasons for why I think the applet should be added (or at least why a more simple applet could be coded):

  • The device connect and disconnect sounds are only registered from within the applet. It’s still up to the user to choose whether a sound is played with the connect and disconnect events. The reason this is necessary, is that for our system sounds contest, a device connect and disconnect sound was made, and users should have the option to register these (rather pleasant sounding) new sounds. After all, the connect and disconnect sounds are great indicators of whether a usb device was successfully registered with Haiku, and can indicate whether a cable is faulty, or if a device simply is not in a state where it can talk to Haiku.
  • I have been looking through the the USB 3.2 specifications, and I think the applet would be a great way to handle “safely unmounting” a usb device, in addition to recommending to a user when their device is capable of higher speeds and just need to be connected to a “blue superspeed port” on their computer. (This was actually suggested in the USB specifications as a “good user experience” feature.)
  • As you mentioned, while the Devices preflet could list the usb devices (and it definitely should be implemented), I think of that preflet as more for “advanced users”. After all, usb devices are very likely connected to the computer externally by an average user, and I feel as though having information about those devices easily accessible could help an average user determine whether their usb connected devices are properly detected and registered with Haiku without using command line tools or digging into the Devices preflet which lists every internal and external device that Haiku has detected.

While I am reconsidering whether using USBDeskbar might be a good idea, I still think a simple applet with the described functionality above should be included in Haiku release images. The applet could even hide itself when there’s no connected usb devices, or if the user desires to save space on the Deskbar. :)

comment:3 by pulkomandy, 19 months ago

The reason this is necessary, is that for our system sounds contest, a device connect and disconnect sound was made

This is not a valid reason. Also, why would these sounds be specific to USB? They would be much more useful with bluetooth, for example, where there are no wires, and it makes sense to have other ways to know if a device is connected or not.

Moreover, the sounds should be configured through the system wide sound preferences and not a specific deskbar applet.

can indicate whether a cable is faulty, or if a device simply is not in a state where it can talk to Haiku.

This should be done with error messages, not just sounds.

I think of that preflet as more for “advanced users”. After all, usb devices are very likely connected to the computer externally by an average user, and I feel as though having information about those devices easily accessible could help an average user determine whether their usb connected devices are properly detected and registered with Haiku without using command line tools or digging into the Devices preflet which lists every internal and external device that Haiku has detected.

I think it is providing users with informations they don't need in the first place. You connect a device, it starts working immediately. You don't need to list it or something like that. Unless you are an advanced user, of course.

comment:4 by madmax, 19 months ago

And we have to fix #16691 before even considering including an USB watcher by default.

Note: See TracTickets for help on using tickets.