Suppose I have a category with 160 images. At 8 images per page, this is 20 pages. Now suppose a user navigated to page 9 in this category and clicked on the first thumbnail to view the image. Then he or she used the "next image" link in the details.html template to view the next 10 images. It would be nice if the user had a way to navigate back to the category thumbnail page containing the thumbnail for the image just viewed.
Currently this user can only click the category link in {clickstream} and then navigate back to page 9 again (assuming they remembered what page they were on to begin with). If the setting in the admin CP only allows 4 page links for the categories template, this user has at least 4 clicks and page loads to do before picking up where they left off.
Does this make sense? Any ideas? My only thought, and to keep it simple, is to enhance clickstream to something like the following:
Home > Category_1 > Subcategory_3 > Page_9 > ImageName
and keep updating {clickstream} with the page number as the user navigates using the previous and next links. Also update the page number if the user changes the images per page setting.
Lastly, and this would be icing on the cake so-to-speak, if the image is displayed in a separate details window, use DHTML to dynamically update the window.opener to display the next/previous page in the category view as the user clicked next/previous in the details window.
