Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Wireframes] Keyword search results with thumbnail-based entries #5957

Closed
drew2a opened this issue Jan 27, 2021 · 6 comments
Closed

[Wireframes] Keyword search results with thumbnail-based entries #5957

drew2a opened this issue Jan 27, 2021 · 6 comments

Comments

@drew2a
Copy link
Contributor

drew2a commented Jan 27, 2021

Below are two variants of wireframes that represent keyword search results.

Keyword search results

@drew2a drew2a changed the title Keyword search results with thumbnail-based entries [Wireframes] Keyword search results with thumbnail-based entries Jan 27, 2021
@synctext
Copy link
Member

good discussion material! Could we have a design sketch with the current result density and inclusion of partial thumbnail results? We will always have some results not having thumbnails and years of transition I fear.

@drew2a
Copy link
Contributor Author

drew2a commented Jan 27, 2021

For this particular situation, I propose using a placeholder, based on the file's extension (auto-generated picture).

We discussed it with @xoriole and @kozlovsky.

@ichorid
Copy link
Contributor

ichorid commented Jan 29, 2021

Is it gonna be infinite-scrolled or paginated?

@synctext
Copy link
Member

infinate scroll is now the industry best-practice.

@ichorid
Copy link
Contributor

ichorid commented Jan 29, 2021

infinate scroll is now the industry best-practice.

Well, it depends... Google still uses pagination. The consensus here is that infinite scroll is better for variable-size items (e.g. Pinterest) and user engagement (e.g. Google Images), while pagination is better for navigation (e.g. Google search, webshops).

However, the biggest problem we got here is that infinite search is, ahem, infinitely slower with QT when implemented with standard widgets, because for every added widget the QT reactor adds all the necessary triggers, etc.

@qstokkink
Copy link
Contributor

Given the latest GUI rework, this issue is no longer relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants