Pau Espin Pedrol <[email protected]> writes:

> I think using Bluetooth device is quite intuitive with FSO. You can enable it
> in shr-settings (so yes, I agree with the idea of no repeating UIs in
> quick-settings for this.)

I'm not sure about that conclusion.  In general the quick settings _do_
duplicate things in shr-settings, and this is useful because it's much
quicker to get to the quick settings.  I personally use quick settings a
lot, and I think it would be good to have a Bluetooth switch there
(under the Network tab, obviously).

(In fact, what would be really cool would be for the quick settings to
be a completely customizable subset of the full shr-settings.  For
example, one thing I frequently need is 500mA charging, when in a car;
but with shr-settings this is quite slow to do:
- go to home page
- scroll so that Settings is visible
- click on it and wait - several seconds - for the main Settings window
- click on Power and wait - a few more seconds - for the Power window
- slide the 500mA slider.

Whereas with quick settings it could be:
- press the power button, to bring up quick settings
- slide the 500mA slider.)

> or use a bluetooth manager which supports FSO (or use
> fsoraw -r Bluetooth app).

Using fsoraw is neat.  But what if there is no app?  In other words, if
everything provided over Bluetooth is a service and doesn't need a UI on
the FR?

But perhaps emtooth is the app?

As I said in my response to Al, I don't fully understand what the scope
of emtooth is, and where the dividing line is between emtooth and
shr-settings.  Could you explain your vision of that?

E.g. is emtooth for setting discoverability, and managing pairing; or
could it also be the place for configuring particular services such
as GPS?

> The only drawback at the moment is that FSO doesn't handle startup of
> bluetoothd when it powers up the bluetooth device, so you need to run it
> manually if you aren't using udev.

I saw a thread where Mickey said that he is going to add this (starting
bluetoothd) to FSO.

Regards,
        Neil
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to