search

Tatoeba / tatoeba2

Tatoeba is a platform whose purpose is to create a collaborative and open dataset of sentences and their translations.
https://tatoeba.org
GNU Affero General Public License v3.0
714 stars 131 forks source link

Allow users to jump more easily between two distant pages #24

Closed loolmeh closed 5 years ago

loolmeh commented 10 years ago

Add "-20" and "+20" to the existing targets for a long list ("<<", "<", x, x+1, ... x+5, ">", ">>").

algoviano, Wall

Original ticket: https://www.assembla.com/spaces/tatoeba2/tickets/416

trang commented 8 years ago

I've changed the title.

Having -20 and +20 would probably still not be optimal. Maybe the user only wants to jump 10 page, or maybe 100 pages away.

I suggest we implement instead the possibility for users to choose which page they want to jump to.

ghost commented 8 years ago

Here it is. You guys just need to choose one: pagination

alanfgh commented 8 years ago

Currently, we have the following:

page_select

This lets people do the following:

(1) go to a specific page within a set of 7 (2) go forwards by one (3) go backwards by one (4) go forwards to the end (5) go backwards to the beginning

Your proposals seem to decrease option (1) from a set of 7 to a set of 5. I suppose that's okay if we need the extra space. I don't know whether your "right-pointing triangle plus vertical line" maps to the existing (2) or (4), but in any case, it drops one of them. I would rather not have us drop this functionality if we don't have to.

I do like the option of a box in which you can type a number. In terms of choosing between the top set, where the right-pointing icon is outside the "Go to page x" box, or the bottom set, where it's inside, I prefer the bottom set.

ghost commented 8 years ago

@alanfgh Thanks for your feedback!

I do like the option of a box in which you can type a number.

This was Trang's idea, and I also like it a lot.

ghost commented 8 years ago

Yesterday Google released the icons I was looking for. So, here they are: pagination

trang commented 8 years ago

One problem I see with the last mockup is that it may not be intuitive for users that they should press enter to go to page 30. I think they will want to click on the >| but will then be redirected to the last page.

@billoliver, since your mockup includes redesign of the pagination elements, I'm going to create a separate issue for it. We should take care of the redesign before we take care of the "go to page".

Edit: created issue #1134.

ckjpn commented 8 years ago

The original idea of -20 or +20 might actually be better than inputting a specific page number. https://github.com/Tatoeba/tatoeba2/issues/24#issue-27745191

With material often being added to tatoeba.org, things are seldom on the same page number as the last time you visited the website, so people don't really know what specific page number they are looking for.

I'm just brainstorming here, but perhaps if we are going to have 5 page numbers displayed, then -5 and +5 might be better "jumps."

Doing this would mean that they are all "buttons" and none of them would require a user to press "Enter".

trang commented 5 years ago

After one year reflecting upon this issue, my conclusion is that it's best to close it. I can somewhat guess the underlying problem that the original feature request tries to solve, but I prefer that we start on a fresh mind. We have to think about pagination on each page separately.

In many cases, allowing to jump to distant pages is not the most practical solution. For instance on a page where items are ordered by date, what the user might really want is to jump to the items that were from 10 days ago. But with pagination, they have to mentally calculate and guess on which page they should jump to, to find items from 10 days ago.

Also, jumping to distant pages assumes that there are many, many pages. But pagination doesn't make sense anymore when there are too many pages. Users reported that they usually don't need to navigate through more than 1000 items (cf. Wall post). So having hundreds of pages isn't really useful.

It's important to allow easy navigation to every piece content in a large pool of data, but pagination is not the answer. It's fine for a small pool, maybe up until 1000 items, but past that we need other tools (basically search and filters).

On a side note, I've found question on UX stackexchange regarding why pagination is not mentioned in the Material Design spec. That's also something to take into account, if we ever decide to evolve our pagination component.