On Sunday 06 February 2011, Neil Jerram wrote: > 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).
Yes - quick-settings is inherently duplicating things that can be done more slowly by going through several layers of the Settings app. That's the whole point - to provide quick access to everyday settings rather than having to go the long way round. > (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.) Better yet a 3-position slider including 1000mA that my car charger is perfectly capable of supplying! I like the ideaof a customisable quick- settings - that way we don't need to argue about what should and shouldn't be there. It would be nice to have a configurable Settings app too, so I could have things in multiple paces and you could have them in only one. Then we just get to argue over which is default ;-) > > 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? emtooth is a bluetooth manager that supports FSO. blueman is a bluetooth manager that doesn't now abut FSO, so needs to be wrapped with fsoraw. I don't want to have to start such an app just to have bluetooth running, so I would go via Settings, quick-settings or even a script that toggles bluetooth policy between auto and enabled. > 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? emtooth is (I think) aiming more for functionality like blueman, but with a finger-friendly interface. It covers discoverability and pairing, but goes somewhat further to cover things like OBEX. I haven't looked at a recent version to see how far down that road it has come. I guess that puts it beyond the scope of Settings, though I suppose that could check to see which bluetooth managers were installed and include a button to invoke one. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
