Dash - “Filter results” should be displayed in the Dash Home

[John Lea]

The Dash home should contain two categories of filters; "Lenses" and "Sources"

The filter category header "Lenses" should contain:

- A list of all currently installed lenses

- By default when a new search is performed, only the Files, Apps, and Music filters should be selected. Note this means that by default when a search is performed *only* the Files, Apps and Music scopes should be queried. Also note that not all the scopes from these three lenses need to be queried (see next point).

- All searches performed in the Dash Home should only return results for content that is instantly available for the user to consume, e.g. the content does not need to be downloaded, purchased or installed. So in the case of Music, only music that is stored on the user's computer or is instantly available for streaming should be returned (music requiring purchase or download being excluded). In the case of Apps, this means that only Apps currently installed on the computer are returned. To implement this scopes need to incorporate a flag stating whether the results they return are 'instantly accessible' or 'an additional action must be performed before the user can consume the content'.

- For each Lens that is selected, a category header titled with the Lens name should be displayed e.g. If "Files", "Music", "Videos" and "Apps" are all selected, four category headers titled "Files", "Music", "Videos" and "Apps" should be displayed.

- See attached wireframe Dash_home_filters.png

The filter category header "Sources" should contain:
- A list of all the different content sources that are available for all the Lenses

[Matthew Paul Thomas (mpt)]

The other bug report is older, and unlike this bug report, it's filed on the appropriate project. So I'm re-marking the duplicate. (John, please don't mark old wieldy bug reports as duplicates of your own newer ones; it slows down development and discourages contributors. See <https://bugs.launchpad.net/unity/+bug/825768/comments/5> for an example of that happening.)

[John Lea (johnlea)]

@mpt; these are different bugs so de-duplicating. Also bug #838127 impacts user facing functionality so should also be subscribed to ayatana-design

[Omer Akram (om26er)]

@John, does it still need fixing with the latest design and stuff?

[John Lea (johnlea)]

@om26er; thanks for the heads up, I have updated the bug description to bring it up to date.

[David Callé (davidc3)]

@john, I see three issues with the proposed design : currently, lenses using web services don't query them when displaying results in the Home dash, and only allow them on lens view, for good reasons.

If every sources become activated by default, each single search in the Home Dash will trigger http calls, which is :
1) bandwith expensive
2) not nice for the content providers who will see their service hammered each time the Home Dash is searched and for the developers who have a limited number of API calls per day on some web services. We don't want services to block the IP adress of Ubuntu users.
3) bad for privacy, as searching for a private local document, will send this query to every web services.

[John Lea (johnlea)]

@davidc3; Hyia, thanks for your comment, sorry for the delay in replying. I have added additional detail to the bug description, does this updated description answer your concerns?

[David Callé (davidc3)]

Thank you John, it does.
The concept of instantly accessible results is an interesting idea and an elegant way of distributing the amount of results and potential http calls between the Dash Home and specific lenses.

It will help the creation of clear guidelines for 3rd party lenses.