Closed juliuskoskela closed 7 months ago
I think this is a good idea!
I would suggest that we would not mount the device to a different folder to avoid additional complexity. We could instead perhaps create a ~/.hydrophonitor
file or a file under ~/.hydrophonitor
folder in an appropriate format where the information about the connected device's path would be saved.
I have two questions regarding the Connect wizard:
I have two questions regarding the Connect wizard:
1. Can we assume that all devices are automounted?
No. The way I see it we can offer the convenience of enumerating the possible (unmounted) drives and the user chooses. Then we mount the drive.
2. How do we detect which device is the Hydrophonitor?
We can't definitively detect that, but we should have checks (that can be expanded upon) to check that there's an /output
folder for example.
I have been thinking about the user flow for figuring out what is the correct device path to give to the
hp-cli
command. For an advanced user this is of course easy to figure out, but for non -advanced users this part can be tricky. Let's review how the user flow would go now.lsblk
to see a listing./dev
.I think this could be cumbersome for the user and a hard user flow to follow correctly for someone not as familiar with the command line etc. I was thinking of the following alternative approach:
hp-cli connect
wizard to connect to the device. This wizard will automatically enumerate attached USB storage devices, scan for /output folder and propose to connect to any attached hydrophonitor. Under the hood a folder is created such as~/.hydrophonitor
and the correct device mounted to the folder.--device
parameter assumed to be~/.hyrdophonitor
or prompts to connect if the device is not found.hp-cli disconnect
to unmount and delete the folder~/.hydrophonitor
.