Probe dictionary should not show all probes by default

[fbertsch]

It's a bit annoying to go to the probe-dictionary only to wait a few seconds while everything loads. Instead it should be blank, and searches should show results.

[chutten]

I think we'd get 80% there if we made the loading indicator non-modal.

[Sylvia23]

@fbertsch I would like to give it a shot. Can I take this up? Thanks!

[fbertsch]

All yours! @georgf you may have some input on how this should look.

[georgf]

I did not see this issue before, sorry. Now i get a better idea of the goal of #538.
I think the probe dictionary should not default to blank and added detail in #538.

There are at least two use-cases to consider here:
(1) existing users that come in with a concrete search
(2) new users that we want to encourage to explore the data

For (2) this should start off with data to play around with, not empty.

For (1), we can't do actual interaction until the data is loaded, but from this i gather we should improve performance / perceived performance.
I wonder how this should work until we have the data loaded?
Show a non-modal loading indicator in the results area but already allow typing in the search box?

[Insiyaa]

What if in the while the data is loaded we display the recent additions?

[georgf]

You mean showing only the most recently added probes?

If i understand you right, then this has the same problem. Nearly all the probe data comes from the same large JSON file (this one).

[georgf]

So, one option could be to:

• Remove the modal loading bar.
• Put a loading bar in the search results area (while we wait for the probe data).
• When the loading finished, hide the loading bar.
• If there is a non-empty search input, show the results.

This mostly works, but has two issues:

• The version filter dropdown is populated from the all_probes file.
• How to handle users that arrive through a detailView link (example)