Pagination in compact mode is not evenly distributed

[bdice]

Original report by Carl Simon Adorf (Bitbucket: csadorf, GitHub: csadorf).

---

In compact mode (only one module selected), the pagination is still divided by the job number, not by the actual number of cards to show per page.
This makes it awkward to navigate large data spaces, where only a few jobs have cards available.

[bdice]

Original comment by Bradley Dice (Bitbucket: bdice, GitHub: bdice).

---

I'm unsure what is the best action to take. This is the same problem faced earlier in issue #13, but just the one-module case.

Currently, we have the following tradeoff:

• Pro: Switching between "list" and "grid" view currently retains the same pagination
• Con: It comes at the cost of having empty or nearly-empty ("sparse") pages if some jobs lack cards.

If we chose a different tradeoff, then:

• Pro: Pages would always be "dense" with content
• Con: Switching list/grid views would have to go back to page 1, and list/grid views would have a different number and layout of pages, based on how many jobs have cards to show.

The second method is certainly more expensive, since we must determine how many total cards there are to show, across all jobs, before we can figure out how to paginate them. This might be expensive, and currently there is no way to get the number of cards that will be output by a module for a given job without actually returning the cards.

https://bitbucket.org/glotzer/signac-dashboard/issues/13/row-for-job-shown-even-if-no-cards-are#comment-43750697

[bdice]

Original comment by Carl Simon Adorf (Bitbucket: csadorf, GitHub: csadorf).

---

I see the issue. Let's put this on hold for now.