touch-packages team mailing list archive

[Pawel Stolowski <1229241@xxxxxxxxxxxxxxxxxx>]

The attached fix for unity8 looks good and will most likely do what it's
supposed to do, but I wonder if this is good strategy. What this change
effectively means is: if scope is currently active (visible) while
network becomes available, it will be refreshed; if it's not visible
(but favorited), it will be marked "dirty" and refreshed when user
swipes/selects it. To my understanding this will affect not only the
after-boot scenario, but normal usage as well. What if network is flaky
and goes offline/online a lot? We'll end up re-querying scopes more
often than necessary, disregarding TTL of the results (currently visible
results may still be "valid", but forcefully refreshed just because
network gets available). Perhaps the shell should cooperate more closely
with shell plugin with this, rather than forcing refresh?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1229241

Title:
  net connection should refresh scopes

Status in LibUnity:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Currently when you start the phone from a fresh flash you get the
  first time use guide.  This blocks networks from initialising.
  Because of this there might not be a connection when the system first
  boots.  This means that click apps and network based scopes and their
  options aren't available.

  Unity should refresh the Scopes once a network connection is
  confirmed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1229241/+subscriptions