In my use case, the new results would all go into new categories. It's not unlikely that some scopes will present a single category; these would also be able to add results without worry.
We already allow results to pop up in arbitrary positions as they come in. Previous versions of my scope retrieved the results one-by-one, and some of these could end up above my scroll position. It's slightly annoying but not that bad, and it would be tolerable in this context too. I think it's fine to leave it up to scope authors to use this in a sensible way, and not disallow it simply because it could be used badly. I don't understand why the user would need to get back to the top of the list of results. Any upwards scroll brings down the header, which provides controls to alter the current query or quit. The only reason you'd need to be at the top of the list would be to refresh the query. But if you've had to summon more results, the current query isn't working so well, so why repeat it? Both of these worries could be addressed by replacing the current results with the new results, instead of appending the new ones. I think that'd feel less natural for the UX point of view, but I haven't tried either. I think this fits just fine within the "quick view of data" mentality. Suppose you have a "nearby businesses" scope that you're using to find a place to eat. You happen to be outside a mall and all n results that the scope loads at first are for the foot court. You shouldn't have to say, "I guess that's good enough." You should be able to easily summon results for a larger radius and find out what else is around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394480 Title: Need a mechanism to load more query results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394480/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
