Poor performance/usability for editing archives

[CirnoT]

Currently, in order to edit archive one has to open the Archive Overview page which loads all thumbnails. For archives with 200+ pages this can (and does) slow web browser as it is now forced to render and downscale hundreds of potentially 1MB+ images.

I believe that we used to have Edit Archive Metadata button directly, why was it hidden behind such a low performance endpoint? I understand that the amount of options is growing however I feel like this should definitely be solved. Possibly we could reuse and enhance image resizing to serve dynamic thumbnails (200px or so in size) instead of full images?

Additionally, I find it increasingly annoying that there is no Back button from edit screen.

[Difegue]

Keep in mind the context menu also has a shortcut to the edit page -- I'll agree that the link should also be easily reachable through the reader.

The overview having poor performance for large tanks is something I'd like to fix, see #514.

I've thought about using the resize functions to save on bandwidth before, but considered they'd probably eat up too much CPU power if having to resize 200+ pages at once.

I think adding incremental loading to the overview to fix the immediate performance penalty is a must-do, and hopefully I can add resized thumbnails to the mix later on.

[CirnoT]

Keep in mind the context menu also has a shortcut to the edit page -- I'll agree that the link should also be easily reachable through the reader.

The context menu isn't available once the archive is opened. I find myself in need of going into edit page more often AFTER opening archive than before (and of course going back to results is no-go either because LRR doesn't remember it)

[Difegue]

I've updated the overlay to use the new thumbnail APIs, which will make it avoid loading the full images from now on.