[scopes] should provide a common "no network" and "no location" error message

[Kyle Nitzsche]

Scopes that use the network or that use location (status for each is provided through the metadata to the scope) usually need to inform the user when there is no network and when location is disabled.

Currently, every scope must handle this on its own, including translations.

It therefore seems efficient for the api to provide translated results for these, perhaps with something like the following text:

"Sorry! The network is not available. Please check your settings and connections."

"Sorry! Location services are not enabled for this scope. Please check the scope settings."

[Marcus Tomlinson (marcustomlinson)]

There is an info() method on SearchReply and PreviewReply objects. This method informs the shell that some non-fatal, warning condition has occurred during the query. This method takes a OperationInfo argument that can be configured to describe a number of warning conditions via an enum such as: NoInternet, NoLocationData, ResultsIncomplete etc. You can call this method multiple times for multiple warning conditions, for example: NoInternet+ResultsIncomplete.

Now as far as I can see by the shell plugin code, we are relaying this information to unity8 via the scope's status() getter, but I don't think it has been decided on yet how the dash would deal with these conditions. I'm adding unity8 to the affected projects.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michi Henning (michihenning)]

Closing this for scopes api, which doesn't know anything at all about translations (and should never know).

[Alejandro J. Cura (alecu)]

I agree that it would be consistent for every scope to show this in the same way, so I'm adding the design team for input.