RFE: (simpler) image gallery viewer?

[intelfx]

This is similar to #173, but much simpler.

Is it possible to turn copyparty into a simple image gallery viewer?

Unlike #173, I don't need anything related to transparent archive extraction. Let's say I have a simple directory with JPEGs and I want to be able to view its contents in full screen one JPEG at a time (with smart alphabetic/numeric sorting) with keyboard navigation and (ideally) a most primitive OSD showing me current file name and my progress or something.

There is a "image gallery with webm player" feature declared in the README, so perhaps it's already done, but I don't see where can I find it. Simply clicking on an image opens it directly in a new tab.

[9001]

The features which are referred to in the readme are the grid-view and the lightbox; you can toggle between the list-view and the grid-view by clicking the 田 in the bottom right, or by pressing the hotkey g . The grid-view can either show thumbnails (default) or icons, and you can toggle between those with hotkey t. All the hotkeys can be seen by pressing hotkey ? -- this shows different hotkey-lists depending on whether a picture is currently open or not.

You can also append ?grid to the end of a link to send someone directly into the grid-view; https://a.ocv.me/pub/demo/pics-vids/?grid

And if you link directly to a picture, then you will also end up in the grid-view afterwards: https://a.ocv.me/pub/demo/pics-vids/#gf-f9f96091

There is currently no built-in ways to strip away the UI components you don't want, but that could be done with custom css if necessary. If you have any specific ideas I can help brainstorm the options :>

[intelfx]

the lightbox

Oh. This is what I wanted. Apparently it only engages if I click on an image when in the grid view — which is why I missed it.

If you have any specific ideas I can help brainstorm the options :>

My only remaining suggestion would be to add the explanation in the README on that demo instance (https://a.ocv.me/pub/demo/pics-vids/README.md) into the main README/documentation, because it's slightly un-obvious.