Opened 13 years ago
Last modified 13 years ago
#209 closed defect (FIXED)
Make next / previous universally non-confusing (possibly with thumbs?)
Reported by: | Christopher Allan Webber | Owned by: | Jef van Schendel |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | ui | Keywords: | |
Cc: | Parent Tickets: |
Description
Right now we have next/previous buttons like: [] The problem: it's confusing. I made a suggestion on how to fix this once, by reversing the order of the arrows: `http://bugs.foocorp.net/issues/423 <http://bugs.foocorp.net/issues/423>`_ However I'm not sure this really makes things clearer. Either ordering is confusing here: - [] is what we used to do but this is confusing because our galleries go in the opposite direction (newer on left, older on right), which is what makes sense for a gallery to be like. - [] is what we do now, but that's also totally confusing. Who really expects arrows to point this way? Not me (even despite filing that old ticket). Imagine reading a webcomic ordered this way. That would be crazy! So here's some suggested resolutions: - Switch back to the old behavior and add text to the arrows, like [] - Add smaller-thumbnail support (75-100px?) and make these thumbnails the navigation. I'd opt for `#1 </issues/1>`_... maybe we can make #2 a different ticket and add an ajaxy "quick browser" like flickr has that's scrollable left and right, and make that **separate** from the current next/previous arrow buttons. Bonus point: doing `#1 </issues/1>`_ will fill up some of that glaring whitespace on those current buttons ;) Dropping this in Jef's lap! Jef, what do you think?
Attachments (1)
Change History (8)
comment:2 by , 13 years ago
Very true, and one way to handle making the next / previous buttons less confusing in that circumstance is to do something like: - /u/cwebber/m/swimmin-with-the-fishes?in\_global\_tags=fishes - /u/cwebber/m/swimmin-with-the-fishes?in\_user\_tags=fishes - /u/cwebber/m/swimmin-with-the-fishes?in\_collection=fishy\_fishy\_fish and use that context to figure out what group of things this is in so that the prev / next buttons are setup correctly.
comment:3 by , 13 years ago
As of now, I've changed it to use suggestion `#1 </issues/1>`_ from the ticket ("Switch back to the old behavior and add text to the arrows"). Here's a small screenshot.
comment:4 by , 13 years ago
Christopher Webber wrote: Very true, and one way to handle making the next / previous buttons less confusing in that circumstance is to do something like: - /u/cwebber/m/swimmin-with-the-fishes?in\_global\_tags=fishes - /u/cwebber/m/swimmin-with-the-fishes?in\_user\_tags=fishes - /u/cwebber/m/swimmin-with-the-fishes?in\_collection=fishy\_fishy\_fish and use that context to figure out what group of things this is in so that the prev / next buttons are setup correctly. If there is another way to create media context streams, I would prefer it. For completely selfish reasons, I am a big fan of sane URLs, and I copy and paste links all day long. An idea would be to provide smart default contexts (if coming from a tag page, then load "all" and "tag" contexts, whereas coming from a user page loads "user" and "collection" [when we get those ^\_~]). I am not sure on how to go about it, but we should ping the general populace on this.
comment:5 by , 13 years ago
Way to go, Jef! The new buttons look great. BTW, GMG looks really beautiful in general.
comment:6 by , 13 years ago
Status: | New → Closed |
---|
Closing this ticket. I think we definitely need to look at what Chris and maiki were talking about above, but that should be a new ticket. To at least have *some* clarity, I've added "? Browsing media by [uploader]" above the navigation buttons. And thanks, Caleb! :)
Note:
See TracTickets
for help on using tickets.