← Back to team overview

ubuntu-phone team mailing list archive

Re: RFC- Having a bluetooth service to handle pairing

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Simon Busch wrote on 03/08/15 10:45:
> 
> On 03.08.2015 11:30, Matthew Paul Thomas wrote: ...
>> 
>> That incoming calls and wi-fi password entry are handled through
>> the notification system is a mistake. It means that without
>> changing the notification system itself, the incoming call dialog
>> can't be full-screen, or display the stored photo of the contact
>> calling you[1]; that third-party VoIP apps, if they existed,
>> couldn't do anything equivalent to the incoming call dialog; that
>> the wi-fi auth dialog can't do anything to prevent you from
>> submitting a password that can't possibly be correct[2]; that the
>> dialog is incapable of showing connection progress, and instead
>> just disappears only to reappear seconds later if there was an
>> error[3]; that even then, it doesn't display an error message[4];
>> and that you can't connect to an enterprise network without
>> opening System Settings[5], because the notification system can't
>> show dialogs that contain multiple text fields and/or certificate
>> pickers.
>> 
>> Repeating this mistake with Bluetooth would result in similar 
>> problems in validating PINs, displaying pairing progress, and 
>> presenting pairing errors.
> 
> Ok, so what would you propose to be the replacement for this?
> 
> ...

That the telephony service open its own dialog for an incoming call
and for a dropped background call, the wi-fi subsystem open its own
dialog for network authentication, the power subsystem open its own
dialog at 10% battery charge, the audio subsystem open its own dialog
for the EU regulatory high-volume warning, the URL dispatcher open its
own dialogs for unknown or contested protocols ... and that the
Bluetooth service open its own dialogs for pairing.

Piping these through a declarative notification protocol can't
possibly do what we want in each case. Whatever technical elegance may
be achieved by avoiding any QML in these services is coming at the
cost of unfixed UI.

- -- 
mpt

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlXAzZ4ACgkQ6PUxNfU6ecpUcQCeMAV9hn9QPHb/Ms/TCc2zhI89
lR4AnRyOMKGMfj1mV2FtPmAX7bdzPEk4
=/rcb
-----END PGP SIGNATURE-----


References