Bug#826329: brltty: Please make easier braille driver setting
Hi,
>
> Do you know that you can also put settings you are overriding
> into /etc/xdg/brltty/brltty.conf ?
I didn't know. I hope it doesn't make things a bit more complex.
>>
>> With capability to check several choices and, for devices, enter it manually
>> (useful when serial device is ttyUSB0).
>
> My question is, how much does this really help to make configuration of
> a non-standard braille device easier? The user still needs to know the consequences
> of their choices, like using ttyUSB0 over a native USB connection.
Indeed. But 1st, the interface could give help info, eg., among choices,
"USB", "bluetooth", "serial port" "USB serial adapter" and "ttyUSB,
please enter the number)). 2nd, even if the user needs to specify info,
he will prefer doing it in a menu than in a conf file. A menu is a menu,
a conf file is "oops, computing syntax, technician language". And in
English. "#? what are #? ... oops complicated".
>> Would it be possible to implement it?
>
> The way to go about this would be to write a debconf interface which
> makes these choices available, and which writes the state of the debconf
> database to /etc/xdg/brltty/brltty.conf.
Why do you prefer /etc/xdg/brltty/brltty.conf instead of /etc/brltty/.conf?
> We've had such code already back in the brltty 3.0 days.
> However, it was dropped because it got a little bit too complicated,
> admitedly because we were trying to *modify* the configuration file,
> which is quite a hard thing to do, if you try to do it right.
>
> We probably need an additional debconf boolean variable which indicates
> if the xdg config file should be written by debconf, or left alone for
> the user to edit.
>
> Most of the devices I see these days are USB, and are well autodetected
> with the default settings in /etc/brltty.conf. I personally don't see
> enough reason to implement this, although I guess I would be fine with
> someone submitting a policy-compliant implementation of a debconf
> interface to brltty.conf.
>
I understand. Here I often see USB displays which need to have driver
explicitly enabled in brltty.conf. Due to USB ID problems. And yes,
there is bluetooth stuff. How can I get the debconf code in brltty 3.0?
I don't know I've skills to twick it, but... why not.
Regards,
--
Jean-Philippe MENGUAL
HYPRA, progressons ensemble
Tél.: 01 84 73 06 61
Mail: contact@hypra.fr
Site Web: http://hypra.fr
Reply to: