touch-packages team mailing list archive

[TenLeftFingers <1500467@xxxxxxxxxxxxxxxxxx>]

Hi Kyle,

Thanks for your response and for correcting the assignment of the bug :)
Regarding #1, I don't think there is an issue with the message app (at
least from the users point of view). The issue is if I send you an sms
now, it will not show on the Today scope until it has done a refresh. I
only mention it to highlight that the refresh requirements of each child
scope differ so much and that this dissonance suggests to me that the
refresh activity should be left to the children.

Regarding #2, thanks for the link. I did go through the few reports for
the Today scope before filing, but not the Day ones.

Congratulations to all involved for a lovely scope. It's now the
'landing' scope on my phone and allows me to use my phone much more
efficiently than my previous iOS/Android phones.

Best,
Jarlath

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

Title:
  Aggregator reloading needs rethinking

Status in Today Scope:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Today scope is basically a place-holder for 'sub scopes'. The
  today scope has three problems which cannot both be resolved under the
  current system. These are:

  1) The scope is reloading at times I do not want it to
  2) The scope has not got the latest data (eg sms message) when I want it
  3) When the Today scope reloads, not only is it slow (BQ 4.5) but it also takes down the entire scope system with it for a few seconds.

  The problem is that when the Today scope refreshes/reloads, it reloads
  all sub-scopes. However, Weather and Today do not need to be reloaded
  for 24 hours at a time (maybe weather is an exception here).

  I think the Today scope should be a 'dumb placeholder' and the sub-
  scopes should be responsible for calling for refresh. The parent
  (Today scope) could then refresh an _individual_ sub-scope using ajax
  or similar. This would improve all three issues above but challenge
  some other fundamentals, eg:

  4) Scopes should be stateless (according to current thinking)

  I would challenge this also, as it would solve the issue where the My
  Music scope shows the user their music sorted by artist, even after
  they have changed it to album sorting.

  The Today scope has come a long way since I got the phone in April and
  I now have it enable since the latest update a few weeks ago. But the
  issues I describe above are 'as expected' behaviour and I think this
  itself is the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1500467/+subscriptions