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

Progress bar for asynchronous requests? #23

Open
stain opened this issue Sep 3, 2015 · 5 comments
Open

Progress bar for asynchronous requests? #23

stain opened this issue Sep 3, 2015 · 5 comments
Assignees

Comments

@stain
Copy link
Contributor

stain commented Sep 3, 2015

Raised by Jaroslav Martasek / Lilly:

As a lot of the results is loaded asynchronously it would be nice if some
sort of progress bar was present.

@ianwdunlop
Copy link
Member

There should be a spinner when things are loading, if it's missing from any of the pages then please let me know. Not sure where the progress info would come from. The explorer asks the api for some results then waits until it gets them

@jmartasek
Copy link

E.g. https://explorer.openphacts.org/search?query=cocaine The spinner spins while the rows are loaded. When related counts are loaded (pharmacology, pathways) these just happen in the background without the user knowing.

E.g. 2 - https://explorer.openphacts.org/compounds/pharmacology?uri=http%3A%2F%2Fwww.conceptwiki.org%2Fconcept%2F13b4b707-8df0-4131-84b4-5433659e6ccf the first load does not have a spinner. The subsequent scroll-down loads do.

@ianwdunlop
Copy link
Member

One of the reasons there are no spinners for the related counts is because they might be 0. Is this information also useful?

@ianwdunlop
Copy link
Member

eg. Here a count of 0 is displayed inside a red badge
explorer-zero-count

Or we could show it similar to how the 'object' view does it:

explorer-zero-is-no

@danidi
Copy link

danidi commented Sep 15, 2015

I would favour the second possibility. The red counts are getting too much attention for something that's not there (but which is not necessarily an error).

Or maybe you could add a search status in the header (next to Compounds 19, Targets 1). Something like:
Searching Compounds...
Searching Targets...
Fetching pharmacology data for compounds...
Fetching pathways for compounds...
...
Finished search.

This way the user would know what data is searched, even if no results are found.

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

No branches or pull requests

4 participants